I need to setup a workflow where tasks and stories are grouped into Epics but the users should not be allowed to set those stories and tasks to a certain state until the Epic is approved by a steering committee. So when the Epic is in a certain state it should trigger the linked tasks and stories to be transitioned to the same state. Can that be done with JIRA?
This is not possible with JIRA out of the box, nor with any plugin I currently know of. There is a popular plugin which offers a number of Workflow Validators: https://marketplace.atlassian.com/plugins/com.googlecode.jira-suite-utilities so maybe asking them for this as a feature request would be an option. It looks like the JIRA PM has said that we don't plan to implement this: https://jira.atlassian.com/browse/JRA-20147
You can check out Misc Workflow Extensions, specifically "Transition Linked Issues": https://innovalog.atlassian.net/wiki/display/JMWE/Post-functions#Post-functions-16-TransitionLinkedIssues(newin3.1.1)
The Epic Link can be found through searches, e.g. issueFunction in hasLinks("is epic of"), or "has epic" also works. This way you can set automated transitions. You can still use conditions provided by JIRA Suite Utilities mentioned by Boris in order to prevent those transitions to be possible/visible until you want them to be.
Thank you Sana. I was able to hide the buttons for Issues that didn't have Epics in a certain state by using Script Runner and JQL conditions with filters as you mention. I have not been able to find a solution how to transition linked issues yet because I primarily want to do that with groovy scripts as well. The plugin you mention seems to have a cost related.
There must be some way of doing this? Can't I include a groovy script or use a listener or something? Or if I create a custom field "Approved" with the options Yes, No & TBD and then set a condition for an Issues in the Epic that it must be Yes to allow transition to further steps? JIRA Suite Utilities seems to have a condition called "Certain value in system or custom field", perhaps that can be used?
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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