Is it possible to make "Include Subtasks" by default checked and Read only?

Krishna P G April 13, 2024

As of now, all the original estimate effort from all subtasks roll up to the Original Estimate for a User Story.

However, If any user unintentionally unchecks the "Include subtasks" in a user story, then the subtasks effort from subtasks of the user story will not roll up to the Original Estimate for the User Story.

So, it possible to make this("Include subtasks") checkbox always checked but disabled(Read only)? Please let me know.

2 answers

1 vote
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 13, 2024

Hi @Krishna P G 

Not natively - the checkbox is always customisable.

A native alternative is to use Automation instead of the checkbox - although this assumes that time is only entered at a Sub-task level, as the rule would "roll-up" the time into the Story's equivalent time fields.

Ste

Krishna P G April 13, 2024

Hi @Stephen Wright _Elabor8_, thank you for the details.

I did try automation and it works but for a newly created customized field. I am unable to rollup the Original estimate of Subtasks into Original Estimate of User Story field.

As you rightly said, I think using a custom field could be a better option as we cannot assume that a user will not log effort at the user story level.

Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 13, 2024

Hi @Krishna P G 

"Include subtasks" is for Time Spent/Remaining Estimate just to be clear, rather than Original Estimate.

You can use Automation to sum the data into the Story. I've put the rule below.

---

You can use a separate field also - but, you can't create a custom time field - you'd have to use either a...

  • Number Field - if you do this, I'd try to choose a denominator which is always absolute (eg. minutes), otherwise you'll have decimal-based results
  • Text Field - and use the smart value ".prettyPrint" to show the result in a suitable format. However, this isn't possible to use for metrics, reports, etc

---

Rule will look something like this...

  • Trigger: Field value changed
    • Fields to monitor = Time tracking
  • Condition: Issue fields condition
    • Field = Issue Type
    • Condition = equals
    • Value = Sub-task
  • Branch: Related issues
    • Type = Parent
      • Branch-Action: Edit Issue
        • Field = Original Estimate
          • Value = {{#=}}{{issue.subtasks.original estimate.sum}} / 3600{{/}}
        • Field = Remaining Estimate
          • Value = {{#=}}{{issue.subtasks.original estimate.sum}} / 3600{{/}}

---

A few notes...

  • I've used "/3600" as my default time unit is hours. The Original Estimate in a smart value is shown in seconds, so you need to divide it into your default unit. 
    • If your default unit is minutes, you would use "/60" instead
  • I found setting just Original Estimate set Remaining without the time calculation - so setting both seems to work more efficiently

---

Let us know if this works!

Ste

 

0 votes
Muhammad Khan April 13, 2024

Yes, it's possible to make the "Include subtasks" checkbox always checked but disabled (read-only) through customization of the user story interface using your project management tool's configuration or scripting capabilities. This ensures that subtask effort always rolls up to the original estimate for the user story, preventing unintentional exclusion.

Krishna P G April 13, 2024

Hi @Muhammad Khan , can you please share more details or any reference link for achieving this using Tools configuration?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events