Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Portfolio Management and Projects in Jira

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?

4 answers

0 votes
Roi Fine Atlassian Team Mar 21, 2018

Hi guys,

There was a similar discussion around how to structure "higher up" issues such as initiatives in Jira & Portfolio. You can check it out here



Very helpful thank you.  One question, does it matter whether you create projects first or issue types?   If a project exists can we add the new hierarchy and issue types afterwards?

Roi Fine Atlassian Team Mar 22, 2018

You can always add additional issue types to an existing project. This document will assist you along the way:


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, or you can email me directly at if you have any questions.

Live sandbox:


Mario O.G

Thanks Mario, looks intersting, though I need it for JIRA Software ...

Hi Martin, 

Just to clarify, Structure is a Jira app, and it works with the Server Edition of Jira Software (but not the Cloud edition). 

[ALM Works]

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?

I'd like to hear the advice on this question also.  I have custom designed a x-initiative, initiative, epoch, story, sub-task hierarchy to suit in excel and now wish to transfer to Portfolio/JIRA Software.   Please advise.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events