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
Could someone please explain how we can create a hierarchy of issues that don't show up on the board besides the parent issue?
For example, We want to complete a profit and loss document. We put the profit and loss document as a task on the board.
One of our members needs the wages to be updated in order for her to complete the profit and loss statement. So she goes into the profit and loss statement task in the board and selects create child issue and types in 'needs updated wages'.
In order for the wages to be updated the boss needs Carlos's backpay to be updated. From here, we want the boss to be able to go into the "needs updated wages" child issue and create another issue that needs to be completed first which is "update Carlos's back pay".
What is the best way to do this sort of issue hierarchy system within Jira and to make sure none of these subtasks show up on the main board but can be accessed only by going down the tree of the parent "profit and loss document" task? Please let me know if you need further explanation of what I'm trying to say.
Jira only supports parent/child relationships (Issue and Sub-task are the words Atlassian uses.) There is no concept of a grand-child or Sub-sub-task. You could use something like Structure to give you the appearance of more layers of abstraction.
Hello @Frank Cecere
After from the suggestion to use plugins like 'Structure'; I would suggest you can even create issues at the same level but create dependencies like 'Blocks' or 'Blocked By'.
Atlassian natively provides this functionality.