Is there any way to configure Jira Portfolio to use custom issue types in project portfolio hierarchies? This documentation page does not explain how to do this. Any the Jira Issue Types in "Portfolio -> Administration -> Portfolio Hierarchy Configuration" do not include any of the custom issue types we have defined.
For instance, for strategic planning purposes, we have a Jira project whose two custom issue types are "Project" and "Deliverable". I would like "Project" to replace "Epic" and "Deliverable" to replace "Story" (functionally speaking.)
I don’t think this is possible. Links between Epics and Story’s are technically implemented in a different way than any other issue type link. As such, Portfolios reliance on it wouldn’t allow for that kind of change. However, I’m not certain, this is an educated guess.
Thanks. I was afraid that would be the case. I would like to understand better how Epics and Storys are special; I mean, I know how they are used in Agile development, but I'd like to understand how that translates into special treatment as Jira issue types. If there are any good links to follow, I would appreciate some pointers. And thanks again.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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