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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,459,205
Community Members
 
Community Events
176
Community Groups

How to change Jira Portfolio Hierarchy within the scope of a single project?

Our company has JIRA for many different project groups. I am running one group and wanted to use Jira Portfolio. The default hierarchy is that both the Stories and Tasks appear under the Epics. I sent  a request to the JIRA admins to update the hierarchy configuration so that Tasks appear under the Stories per https://confluence.atlassian.com/jiraportfolioserver/configuring-initiatives-and-other-hierarchy-levels-802170489.html since that is how we organize our projects: Epics have Stories and Stories have Tasks/Sub-Task. We don't want Tasks under Epics. We want to be able to organize tasks under each story in Portfolio view and not have them be mixed up with the parent stories on the same level. I know I could hide tasks from view but that is not what we want, We still need to see the tasks, but under its parent story.

The Jira Admin stated we can't do this, as this change would affect all other Portfolio projects created in other JIRA projects (meaning, I'd have to track down owners of hundreds of Jira projects and see if this change would be acceptable). That is just not feasible. The documentation link above does state: "Note that any changes you make to the hierarchy levels in Portfolio for Jira will apply to all existing Portfolio plans." Or is this statement just badly worded and they really mean to say that a hierarchy change would apply to all existing plans created within the scope of a Jira project? If that is what is meant, it makes sense and is ok.

So, Is there a way to change the hierarchy for Portfolio within the scope of one Jira project. I can't be the first person out there to wanting to use a different hierarchy than other projects in a large organization, right?

Many thanks in advance!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events