Hello!
I have this really hopeful dream to have some sort of automation to fetch me data from a child issue and have it displayed on a specified field in the parent card.
Hello @Mireya Cintora
You mention you want to do this for parent/child issues. What are the actual issue types? Are you talking about standard issues (i.e. task, story, bug) and their subtasks? Are you talking about Epics and their child issues (which are standard issue types)?
You can definitely create Automation rules to fulfill those requirements, but I would ask you to consider what problem you are trying to solve by doing this, and is there a better solution?
There are third party apps that can help generate roll-up information without creating custom fields and creating new automation rules. Perhaps that would be a better solution.
Automation Rules would require you to add more custom fields. Updating the fields in real time with the changes happening in the child issues could result in a large number of automation rule executions.
Is this for just one project or many projects? If this involves Team Managed projects and Company Managed projects you would have to have different rules for each Team Managed project.
@Trudy P Claspill
They are the Epics and their child issues. I did look into the third part apps but at the moment my employer wants to limit the amount of these third part applications, so I must find a way to do with automations.
Updating the fields in real time with the changes happening in the child issues could result in a large number of automation rule executions. - Would that run our project/issue slower?
This will just be a for one project that is Team Managed.
Hi @Mireya Cintora
If you would be interested in an app to help with roll ups of numeric fields, you may want to try our plugin.
Issue Hierarchy
The app shows your linked issue hierarchy in a tree view. The app can help you easily Sum up values (time tracking/story point/custom numeric fields) to see overall progress for your Issues at each parent level, in percentage terms.
Also it allows to filter your linked issue with custom JQL and grouping at parent level as well.
In the example below it shows the child issue statuses at each parent level.
(Disclaimer: I work on RVS, the vendor for this app)
I have not heard that Automation Rules cause other project/issue processing to slow down.
You should check with your administrators about the potential for the execution of these rules (there will be more than one) combined with any other rules that run to bump your instance over the usage limit for Automation Rules. Refer to
https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/
I have some additional questions about your requirements.
1. Field that counts the total amount of child issues as they are created
If a child issue is removed from an Epic, do you want the count of child issues in the Epic updated?
If a child is added to an Epic at a later date (after the creation of the child was completed) do you want the count of child issues in the Epic updated?
2. Field that adds (or average) up the amount of money recorded in each child issue, and displays the total on the parent. Honestly just running data or averages as our child issues deal with money.
You need to define this requirement. Do you want the amounts from the child issues totaled and displayed in the Epic, or do you want an average displayed in the Epic? If an average, how do you want that calculated; total of amounts in children divided by number of children?
Do you want this value to be updated as child issues are added and removed from the Epic?
Are the values in the child issues subject to change? If they change, do you want the information in the Epic updated?
Field that counts the amount of child issues in each status (To-Do, In-Progress, Done).
Are those the only statuses used in the child issues? Are those all the statuses used by the child issues?
Is the workflow likely to be changed so that any of those statuses are removed, or new statuses added?
Do you want these counts updated as the child issues move through their workflows?
Do you want these counts updated if child issues are added/removed from the Epics?
Thank you for the automation heads up, we indeed are about to hit our max amount of rules ran for the month.
1. If a child issue is removed from an Epic, do you want the count of child issues in the Epic updated?
2. Do you want the amounts from the child issues totaled and displayed in the Epic, or do you want an average displayed in the Epic? If an average, how do you want that calculated; total of amounts in children divided by number of children?
3. Are those the only statuses used in the child issues? Are those all the statuses used by the child issues?
It looks like you're new here. Sign in or register to get started.
