I have an interesting issue that I honestly am unsure of the best place to start from.
Essentially I have a ticket hierarchy laid out like this
Initiative and Features are always out of the same project but the epics come from many projects.
All of these are linked via a Parent relationship.
All of these ticket types share a common field called 'Status' (text box) which is used exactly for that, entering a status in text form. Such as 'XYZ Team is finished with ABC and will begin Task D next week' etc
What I would like to do is roll up the Status from all child tickets Status field into the parents Status field.
So if a feature has 5 child epics all 5 of those Status fields from the children end up in the Status field for the parent basically (wihtout overlapping each other.
I realize that to build this out dynamically (every time one status field is updated only that portion is updated in the parent) would be a nightmare of unimaginable proportions to create so I am ok with this being a timed pull. Basically once a week the status on parents is cleared out and all the children statuses are re-pulled in.
Any thoughts? Thanks in advance!
Hi @Travis Hill
I'm not a marketplace entrepreneur, but we're currently evaluating the plugin JXL.
It does the exact thing for you: you can have a summary line on each hierarchical level that you want. It works flawlessly with the system status field, so you would need to amend your workflow to mimic the statuses mentioned in your post.
Mind you, that complete freedom of the status field by text entry will hinder a clean sum-up, hence the JXL solution using the system status field that is populated by the workflow.
Final cherry on the cake: this solution is dynamically.
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Travis Hill ,
If I understand correctly, would this help?: https://community.atlassian.com/t5/Jira-questions/Automatic-update-of-a-new-field-based-on-values-in-another-field/qaq-p/1043616
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for this. Its close, but not quite what is needed. What im looking to do is summarize multiple text fields on multiple tickets into one singular text field on a singular ticket
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.