we are looking to implement a basic (essential SAFe) hierarchy with Portfolio

[koteswararao]

we are looking to implement a basic (essential SAFe) hierarchy with  Portfolio :  Epic – Feature- Stories- (sub task/task ) Current issue types are Subtask, Story, Epic in Jira.

So I tried to get him do declare in portfolio an issue type labeled “ Business Epic” – of issue type of Epic, a “Feature” – of issue type of Epic with parent Business Epic.

He cannot do this. Am I correct or we are missing something ? 

Also I don’t remember if we needed to declare a “Story “ – of Story issue type, with a parent of Feature.

(I really don’t remember this, I think we didn’t but then how will the story know its parentage … hm… and could have been changed in the last 2 years anyhow)  If I would have admin rights I would play with it but I cannot.

Can someone help us out to understand this ?  And help us create some instructions for the admin how to do it ?

[Earl McCutcheon]

Hello,

First I recommend checking out this Blog Post and white paper that discusses SAFe methodologies in Jira, as well as Portfolio Integration with SAFe:

• Scale agile practices with programs in Portfolio for Jira
• Scale agile with our Atlassian and SAFe® for teams white paper

For the Hierarchy Portion of your question specifically its going to be the  Initiative levels above the Defined "Epic >> Story >> Sub task" established hierarchy in Jira Software, and  this lines up with the following community posts on the topic:

• https://community.atlassian.com/t5/Jira-questions/Optional-level-in-hierachy-in-Portfolio-for-JIRA/qaq-p/658892
• https://community.atlassian.com/t5/Portfolio-for-Jira-discussions/JIRA-Portfolio-supporting-SAFE/td-p/762103

Regards,
Earl