I am new to Jira and trying to implement simple Scrum:
Epic > User Story > Tasks.
Where the Story has the same workflow as the Tasks. If one of the Story's tasks in a spring, so is the Story... and when all associated tasks are done, Story is Done.
Actually, in an ideal world I'd have: Epic> Story > Criteria > tasks.
Unfortunately, in all my search, I've only found that Jira supports:
Epics > User Stories > Subtasks
... and these Subtasks don't even show up in the backlog view !!
This seems like obvious functionality that I must be missing... can someone point me in the right direction?
Any help would be appreciated.
If the answer involves "experience programming"... that's fine. Please tell me what needs to get done and I'll hire someone :).
Thanks for the suggested reading. Yes, creating an Epic from and Epic is possible but no way to relate both Epics to each other unless you do it manually for each Epic, much like how you need to relate a Task to a Story manually for each Task.
Jira seems like an immensely powerful tool with customizable issues, workflows, screen, schemes etc. but it seems to be falling down flat on its face on this most basic functionality. And it seems users have been asking for this for years (from articles I have seen in my due-diligence).
What a bummer.
Yes, this is true.
This should have been an obvious flow to have EPIC -> STORY -> TASK
But seems the STORY -> TASK linkage is not present.
Would be raising to Support, just in case they can highlight something missed by me.
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