Cloud Migration Resources
Planning a Jira Cloud migration? These resources can help you get started:
→ JMWE Cloud features – Review Cloud features and understand key differences between DC and Cloud.
→ Migration support from Appfire – Learn how we can help you migrate smoothly.
Move parent and child issues together in the workflow
In this recipe, you will learn how to move the parent issue and child issues together. Here the Parent-Child relationship can be
Jira Software “Parent-Subtask”
Jira Software “Epic-Story”
Advanced Roadmaps (Portfolio) “Parent link”
Issues linked through the links available in “Issue Linking”
Consider a case where you want to move an issue to the same status as its children, when all of its children have the same status (e.g. all children have been move to “In Review”). Additionally, you do not want to close the issue until all of it’s children are closed, and you want to close the parent automatically when all children issues have been resolved.
What do you need?
JIRA Administrator login
Workflow, as shown in Figure 1
Configure
Consider the following workflow shown in Figure 1, right.
Step 1: Add the Transition related issues post-function to the “In Progress” transition
Add the Transition Related Issues post-function to the “In Progress” transition of the subtasks workflow
Under “Which Issues” select
“Parent issue of the current subtask” for Jira Software Parent-Subtask
“Epic of the current issue” for Jira Software Epic-Story
Select “Parent issue of the current issue in the Portfolio hierarchy” for Advance Roadmaps (Portfolio for Jira)
Select “Issues linked to the current issue through the following link type” and the link in “Issue Link” for System links (Issue Linking)
Using the “Transition Picker” select the “In Progress” transition of the Parent workflow
Select "Conditional execution” and input for the following script
relatedIssue.status.name != "In Progress"Save the post-function
Move the post-function after “Update change history for an issue and store the issue in the database” built-in post-function
Step 2: Add the Transition related issues post-function to the “Done” transition
Add the Transition Related Issues post-function to the “Done” transition
Under “Which Issues” select
“Parent issue of the current subtask” for Jira Software Parent-Subtask
“Epic of the current issue” for Jira Software Epic-Story
“Parent issue of the current issue in the Portfolio hierarchy” for Advance Roadmaps (Portfolio for Jira)
“Issues linked to the current issue through the following link type” and the link type (eg: “is blocked by”) in “Issue Link” for System links (Issue Linking)
Using the “Transition picker” select the “Done” transition of the Parent workflow
Select the "Conditional execution” and input for the following script
issue.subTaskObjects.every{it.status.name == "Done"}Save the post-function
Move the post-function after “Update change history for an issue and store the issue in the database” built-in post-function
Publish the workflow
Step 3: Hide transition “Done” until all the subtasks are in Done status
Add the Related Issues Status Condition to the “Done” transition of the parent workflow
Under “Which Issues” select
“Sub-tasks of the current issue” for Jira Software Parent-Subtask
“Issues that belong to the current Epic” for Jira Software Epic-Story
“Child issues of the current issue in the Portfolio hierarchy” for Advance Roadmaps (Portfolio for Jira)
“Issues linked to the current issue through the following link type” and the link type (eg: “blocks”) in “Issue Link” for System links (Issue Linking)
Select “Done” status “Status(es)”
Save the condition
Publish the workflow