You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is there any way to close parent issue irrespective of issue type where all the child issues status are in Done stage.
As you can see in the above snap, it "Closed" Epic parent once all child issues are "Done".
But what if the parent issue type is "Improvement", "New Feature" etc.
Thanks in advance!
When you say child issues, you mean subtasks, right?
So then, this should work:
I realize that's from Jira Cloud and I think you're on Server or DC, but I believe this should work there too.
Whoops! I forgot the last bit of that rule, where you change the Parent status to Done.
But also, there's a Template that's similar to this:
Hello @Darryl Lee
For child as Subtask is possible and working too.
But in my scenario, child issues are of "Improvement","New Feature","Task" etc. type.
And there is no branch available for this, either Epic parent or Subtask is possible not other issue types.
I think there may be a misunderstanding of relationships and types here, and I think it's worth just explaining that there are several different relationships that issues might have with each other.
The language in this area is also fuzzy, even when talking in Jira-speak. I am actually going to avoid using the phrases "parent" and "child" because while they make sense, they do not always make clear what the differentiations between relationships are.
Jira Software has a three level hierarchy: Epic -> Issue -> Sub-task
Hence, there are three relationships that could be formed:
The important point here is that these relationships are done totally differently in Jira. The relationship between Epic and Issue in Jira is totally different to the relationship between Issue and sub-task.
This means you need to consider the type of relationship the issues have whenever you are doing searches or configuring things that rely on relationship.
So, bearing in mind that Issues (stories) are not sub-tasks of their Epics, you need to look at what relationship you are trying to select for. Is it the Epic -> Issue, or are you looking at Issue -> sub-task?