We are using BitBucket with Jira Software. We have created parent issues and child issues attached to it. When we change the status of the parent issue, it doesn't change the status of child issue. Going through the workflow - when deployment has been completed, parent issue changes to Deployed on DEV, but child issues remain in their own status.
What's the best way to ensure that child issues follow the flow of the parent issue? I tried to look at automations, but can't see anything along those lines.
@Trudy Claspill Hi Trudy, I tried the template you suggested above, but when I update the Epic (Parent) ticket to Done, the child issues remain untouched. I'm not sure why there status is updating when I update the Epic ticket. Thoughts? Thank you!!!
The template I highlighted is for issues and subtasks, not Epics and child issues.
There is another rule in the Automation Rules library playground for closing child issues when an Epic is set to Done. You could use that as a guide to create a new rule in your Jira instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Artur Leonowicz
Welcome to the Atlassian community!
Have have you created the parent/child relationship between the issues? Are they Epic and child issues, or standard issues with subtasks, or something else?
On your own system if you go to Automation and select Library you can find a template rule for closing sub-tasks when the parent issue is complete.
In the Automation Rules library playground you can find many other example rules.
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.