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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
in this Documentation is a Screenshoot which shows that Epic and User Stories can be assigned to different Hierarchy Levels, so that User Stories can (from a Hierarchy Level view) put underneath Epic but separated and put above all other Standard Tasks.
Jira Portfolio Server 0318 - Configuring Hierarchy Levels
In our Installation (Server Version 03.20) there is no possibility to adjust Hierarchy Level for User Stories in a way that they are below Epics. Epic Level is predefined with Ticket Type Epic (grayed out) and can't be changed.
I do have only the option to add User Stories to this Level on top or create a Hierarchy Level for User Stories higher than Epics - which does not really makes sence.
Any Ideas/Hints out there?
best regards, Steffen
Seems that just the Hierarchy Level is named "Story" and contains all Standard Issue Types, including Tasks.
This is correct - each hierarchy level has its own name, but you can rename the hierarchy level from "Story" to something else if you'd prefer. You do this from the hierarchy configuration page:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.