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
Hi, Just wondering if there is a way to structure Story/Task/Sub-Task relationship?
At the moment when creating a Story, I can only create Sub-Task. Can I structure so that under the Story, I could create Task and under the Task, would be a Sub-Task?
No, you will not be able to create that structure in Jira. Task and Story function at the same level and cannot be children of each other.
To add (a little) to what John said, you cannot with Jira out-of-the-box. However, if this a requirement for you nonetheless, it can be done with an Atlassian Marketplace app (apps that add additional functionality to Jira).
If this is the case for you head over to the Atlassian Marketplace and try searching for Jira apps, on cloud, that offer "custom hierarchies."
Hope this helps.
The fact that this is still such an OOTB restriction is incredibly annoying though. Atlassian decides the structure we can use, end of story? We have to turn to other people who were also so fed up with it they made workarounds?
It seems at this point, if they ACTUALLY cared about their customers needs, they would implement something that enough of the community wants, instead of trying to "but, but, but the internet says you should do it this way!" BS us.
This is not the first time I've run up against an Atlassian problem where they literally just ignore the entire community, and just act like "get rid of us, see how much THAT costs you, guess you're stuck!".
If I could, I'd tear it all down at this point and find better companies for our SDLC needs. Terrible community relations
Hi @Simonas Murauskas ,
Jira has 3 issue types like Epic, Base, Subtask.
Task and story both are base issue types (standard issue types).
As per my knowledge, you can create same issue type (base type) request under other base issue type. like you can't create story under task or task under story like that.
EPIC --> Base or standard issue type --> subtask
Out of the box, you can create base issue type under epic and subtask and base issue type.