We have a requirement where in we have 3 independant workflows: Change Request(CR),PBI and SBI.
Suppose in CR workflow we come to a state "Approve" we could like to invoke another workflow"PBI workflow". CR being task and PBI being subtask. In PBI workflow we reach a state "In progress" then we invoke another workflow "SBI workflow" this being subtask of PBI. Once all SBIs gets completed then PBI will get closed. This in turn transfers to the CR workflow which in turn reaches a state closed since all the PBIs are completed
Sub-tasks creation are possible for 1 hierarchical level right. I meant if we have 3 issues types namely A,B and C. Then we can make C as a subissue type under isssue type B by using the subissue feature of jira. But if we want to extend to one more level wherein B can be made subissue of A this is not possible since C is already made a subissue of B. JIRA allows for 1 level of hierarchy classification. How can we extend this? A->B->C - level
Yes, there's only one layer of sub-task available in Jira. You can't extend that without rewriting Jira.
There is a plugin available called "structure" which sort of does this. It's not quite sub-tasks of sub-tasks, but your users will effectively see it as that.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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