# API return whether "Include subtasks" is checked

**URL:** <https://community.developer.atlassian.com/t/api-return-whether-include-subtasks-is-checked/50837>\
**Category:** Jira Cloud\
**Tags:** jira-cloud, rest-api\
**Created:** [August 9, 2021, 11:55pm UTC](https://community.developer.atlassian.com/t/api-return-whether-include-subtasks-is-checked/50837 "2021-08-09T23:55:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RhysDiab](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/rhysdiab/32/38004_2.png) [@RhysDiab](https://community.developer.atlassian.com/u/RhysDiab)\
**Post date:** [August 9, 2021, 11:55pm UTC](https://community.developer.atlassian.com/t/api-return-whether-include-subtasks-is-checked/50837/1 "2021-08-09T23:55:04Z")

</div>

For the purpose of my app’s estimate roll up, I’d like to know if a user has checked 'Include subtasks" when logging time against an issue.  
At the moment I can’t find this in the API.

![include-subtasks](https://global.discourse-cdn.com/atlassiandeveloper/original/3X/7/6/7645b468d9b7eb391b69325e896871056122b696.png)

Whether it’s checked has implications for how estimates are rolled up from one level to another.

Is there somewhere in Jira Cloud’s API where I can find this data?

Best Regards,

Rhys

---

<div class="post-metadata">

**Author:** ![anon96974232](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@anon96974232](https://community.developer.atlassian.com/u/anon96974232)\
**Post date:** [August 10, 2021, 1:14am UTC](https://community.developer.atlassian.com/t/api-return-whether-include-subtasks-is-checked/50837/2 "2021-08-10T01:14:04Z")

</div>

Hello @RhysDiab

There currently is no Jira REST API endpoint that allows you to get the value of the _Include Subtasks_ option for time tracking per user. Refer to [this previous question](https://community.atlassian.com/t5/Jira-questions/Get-Time-Tracking-information-for-Story-that-includes-sub-tasks/qaq-p/622221) on the same topic.

Maybe look through the Jira Cloud feature requests and, if nobody else has already requested it as a feature for the REST API, you can log it.
