Can my custom field be a parent issue?

[Deleted user]

We are moving to SAFe Agile in my department, and I am attempting to modify Jira to have a "Feature" vs an "Epic" since "Epic" has a different definition in SAFe terminology.  We tested a translator plug in but it would universally translate vs translating only for our project.

I created a custom "Feature" field in Test, but I am unable to link other issues to it as I would link them to an Epic.  The issue type is set as "Standard" vs "Sub-Task".  Is there another setting I should be checking?  How do I get my custom field to act like an Epic would in terms of linking?

[Nic Brough -Adaptavist- · Accepted solution]

You won't get another field to work like Epics directly, but to add to the other answers here, you could also look at Structure or Portfolio apps - Structure allows you to define more layers, and Portfolio directly implements features and initiatives.

[Deleted user]

Thank you!  I think this is what will work best for us, I was able to find some additional PDF documents on implementing SAFe in Jira as well :-)

[Johan Soetens _Dumblefy_]

Hello Elizabeth,

create a new Issue Type Feature instead of modifying your Epics.

You might also be interested in Jira Align (formerly AgileCraft).

[Deleted user]

Thank you, I did create a custom field of "Feature" as I mentioned above, but I will also look into that Jira Align.  I appreciate the response and help!

[Johan Soetens _Dumblefy_]

You're welcome.

Out of the box, you will not be able to recreate the same functionality (UX) as with an Epic but a simple solution is to create a new Issue Type Scheme with Release and sub-tasks. Also connect your screens using a new Issue Type Screen Scheme