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 anyone help us with ideas on how to create Theme and Initiative items in Jira? See that on the Atlassian website these levels are described.
Below is the website link:
In the software (jira and Confluence) we only identify the EPIC, STORY, TASK, SUB-TASK levels.
That's incorrect. Jira Software only has levels of Epic, Issue and Sub-task. Stories are at the issue level, as are Tasks by default (but some admins rename Tasks and then create Task at a sub-task level)
To get Themes and Initiatives, you're going to need apps to create the two layers above Epic.
Atlassian has Jira Align aimed at large scaled agile installations, and Advanced Roadmaps for smaller users. Structure is another option for Cloud, as it lets you layer issues aorund the existing levels.
Hi, @Patricio Ibarra. No. Unless you already have Jira cloud premium, or Jira data center.
If you do not, upgrading to one of those platforms would be more expensive than a plug-in.
Hope this helps,
Hi, @Domenic Wiley. Welcome to the Atlassian Community.
It takes a little getting used to, but think of Structure as a blank slate where you may arrange Jira issue types in any parent-child relationship you wish -- and visualize those relationships in a work breakdown structure where the relationships are clear by the way things are stacked and indented.
To Jira, an Initiative is just a new/custom issue type that you create (it's no different — to Jira — than a story, or a bug, or a task, or any other issue. But when presented hierarchically is a structure board they become the apparent parents of the subordinate issue types.
You have to be careful about where Epics and Subtasks live in the hierarchy though because those are special issue types in Jira.
Reach out to the Structure team for a demo if you'd like. They'd be happy to walk you through your use case(s). You can reach them via email@example.com.
Hope this helps,
That's correct, Dominic. But you do not need to have Advanced Roadmaps to do what you describe.
Don't get me wrong, there is nothing wrong with Advanced Roadmaps, it's a great/useful product — but it is not required for creating the hierarchy you describe.
Drop us a note at the email above. A 15-min. demo will accelerate things for you. Or, if you prefer, we have monthly demos for all new users and evaluators. They're called called Structure Sessions. See the comment by @Amy Ou in this Atlassian Community thread for more information.