Enable Feature Records in Jira Next Gen

Alex Grass March 16, 2021

My organization uses Jira Next Gen. Right now, we are only seeing the ability to create Epics and Stories. Is there a way to configure Jira Next Gen to allow for the Creation of Feature Groups or Feature records? We would like to use the Feature record as a 2nd layer in our 3 layer hierarchy (Epic, Feature, Story).

I know the Feature option was available in Jira Classic, but we are having a hard time finding this in Next Gen. 

Any help would be greatly appreciated, thanks! 

1 answer

1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 17, 2021

Welcome to the community

Jira Next-gen does let you create your own issue types, so yes, you can add features.

But neither Next-gen nor Classic allows you to change the heirarchy like that.  It's sub-task, story, Epic.

Advanced Roadmaps and other apps can give you layers above Epic, but you'll need to build something with scripts and automations, or use Structure to get something to look like it's in-between Epic and Story

Dave
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 17, 2021

Worth pointing out that at the moment Advanced Roadmaps does not support Next-Gen projects (it's only possible to add additional hierarchy levels for Classic Projects).

However, there is a workaround with hierarchy worth sharing.

You can rename hierarchy levels and place additional issue types in them. So for example you can rename "Epic" to be "Feature"

Screen Shot 2021-03-18 at 9.33.32 am.png

And then create new issue types called "Feature" and "_Epic" (you can't reuse the epic name unfortunately, nor can you move the default Epic type to another level)

Then you can create that hierarchy in plans:

Screen Shot 2021-03-18 at 9.33.06 am.png

 

Screen Shot 2021-03-18 at 9.33.16 am.png

This does mean that your new "_Epic" issue type won't behave like an epic does (i.e. it won't appear in the sidebar of the backlog) but that might not necessarily be a concern for you - it really depends on you use case!

Regards,

Dave

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events