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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am assessing if Portfolio for JIRA will meet my team's needs. I am interested in the functionality available with the hierarchy function. Using the example in the online guide, I want to create a new higher level called "initiative." If I follow the guidance correctly, i will create a new issue type called "Initiative" and then associate that level with lower levels such as Epics, Stories,and sub-tasks. My question: am I able to implement a workflow for the Initiative level issue type, separate from workflows for the Epics, Stories, sub-tasks, etc.?
Hi @John Bobeck,
As you mentioned this will be a new Jira issue type which means you have full control over it, and you will be able to use a Workflow scheme to associate this issue type with a specific workflow.
The same applies if you want to create more than one hierarchy level above Epic in Portfolio.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.