We have a business requirement to update value of a custom field in a JIRA project based on the resolution status of all linked tickets. So when all the linked tickets are resolved, we have to update the value of the custom field to resolved. Otherwise, even if one of the linked tickets is not resolved, the value of the custom field will remain 'In progress'.
We have a project called "Escalations" where a business user can create an issue, for example JIRA number "ES-20". We have a custom field, "Resolve Status" in Escalations project and the moment ES-20 was created, the value of "Resolve Status" was set to "In Progress".
Now, upon investigation by development team, they decide that ES-20 actually is a bug in software and will require changes to backend as well as frontend. We have a separate project for backend (BE) and separate for frontend (FE). So they decide to create 2 issues in backend project (BE-31 and BE-32) and 1 issue in the frontend project (FE-44). Then they link these 3 issues to ES-20. So ES-20 now has BE-31, BE-32 and FE-44 linked to it. Development teams then separately start fixing the issues and once all 3 issues are fixed they mark it resolved. The moment BE-31, BE-32 and FE-44 (all 3 of them) are resolved, the value of "Resolve Status" custom field on ES-20 is updated to "Completed". The status of ES-20 will then later of be set to Resolved, manually by development team. Is it possible to update the value of "Resolve Status" custom field?
I think this could be done without much code using workflow trickery and the Misc. Workflow Extensions plugin. To simplify, i'll call the issues Child and Parent. I'd investigate something like this:
So basically, you want the child issues to try and transition the parent issue when one of them is resolved, and you want the parent issue to validate it can transition, or to prevent the resolution from changing at least.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
It takes a village to identify, fix, and communicate about incidents. While developers and SREs work hard to get things up and running, support and marketing teams communicate with customers. Yet whe...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs