How-To? Custom field roll-up from Sub-Task to Parent

[JSams (old account)]

Hi community. I'm working on a personal project to standardize the way my team at work does what we do. The way I run my projects is I have parent issues, (Stories, Bugs, Improvements) and I do my work on Sub-Tasks. We use the Component and Label fields to identify whether something is config work, engineering work, integration work, or plain old to-do (component) and what object the work is affecting (labels).

What I'd like to figure out is if there's a way to use those fields on the Sub-Tasks and have those roll up from all Sub-Tasks and concatenate on the Parent. Don't know if it's possible, but if it is I'd really like to know.

[Bill Sheboy · Accepted solution]

Hi @JSams (old account) -- Welcome to the Atlassian community!

Yes, you can do that using automation rules.  When something changes in the sub-tasks, you can use that as a trigger to roll up the values into the parent.

To get you started, please see this information, including some similar use cases:

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

https://community.atlassian.com/t5/Automation-articles/How-to-sum-up-logged-hours-using-automation-in-Jira-Cloud/ba-p/1409115

Best regards,

Bill

[Jarod Sams]

Oh this is perfect. I hadn't thought about using Automations. I just set up a couple and they worked perfectly. Thank you!

[Bill Sheboy]

I am glad that helped you, Jarod.  Please consider marking this question as answered so others can find it easily later.  Thanks!

[Vincent Mutambuki { Mumo Systems }]

if all fails, There is also Abacus which has defined actions that can be used to roll from subtask to parent and issue to epic.