Perhaps I'm just not seeing a better way to do this.
In my project, I'd like to have some flexibility with Portfolio's hierarchies, in that, I'd like to have Initiatives, but with the ability for them to have both Epics and Stories as direct children.
Does not seem like that's possible, and the doc doesn't provide any added clarity on such a configuration. Perhaps I can simply use Epics and don't need the Initiative level?
Hello @Kenny Kutney
I am using portfolio 2.1.5 (hosted) and it's possible to have Epic and Story at the same level and add another level on top of it. Why don't you upgrade your portfolio on Cloud and do the configuration in the "Admin" section of the portfolio and change the hierarchy as at any level you can add multiple issueTypes for that level.
Thanks, Tarun. Running Portfolio 2.1.6 (Cloud). If you (or another reader) can share a description (or image) of having multiple issueTypes on a level, I'd appreciate that!
I've tried setting the Epic level to Epics and Stories, but that flattens out the hierarchy (so I no longer see any stories "under" an Epic).
Hopefully, I'm not setting it up correctly...
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs