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 I'm new to Jira.
I think it's very simple from a development team perceptive to use this tool.
My concern is management, they would like to see the work "Roll Up" into their roadmap or initiative.
So, before I start using Jira, wouldn't it be best to start with Portfolio for Jira to define the Road Maps or Initiatives first, then define issue sources to be pulled fro Jira?
I'm also concern about managing the Portfolio as a separate project, especially if we have to have a custom hierarchy.
What is the most effective way to us both?
You can always add additional issue types to an existing project. This document will assist you along the way: https://confluence.atlassian.com/jiraportfolioserver/configuring-initiatives-and-other-hierarchy-levels-802170489.html
Hi Carlos, and Martin.
If you guys are still looking for a solution, please consider giving Structure for Jira a try.
When it comes to project management, Structure gives you an overview of your Jira issues and projects. You can either create your structures manually or automatically by using Structure's Automation feature. Click here to read more about it.
With Structure, you can come up with different types of hierarchies, allowing you to have a "roll-up of issues from the top down."
Structure for Jira is also packed with other easy to use features that help Atlassian's largest customers track, manage, and visualize progress across projects. Currently, it is compatible with Jira Server (Data Center and Service Desk), but we are actively working on developing a version for Jira Cloud.
I’d be more than happy to tell you more about Structure, if interested. Please feel free to reach out to our support team at firstname.lastname@example.org, or you can email me directly at email@example.com if you have any questions.
Just to clarify, Structure is a Jira app, and it works with the Server Edition of Jira Software (but not the Cloud edition).
I was also expecting to make all x-initiative and initiative types as Project types and each to also have a Board. These boards in a hierarchy should I hope then allow me to perform the consolidation/roll up from the top down. Does this make sense will it work?