Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Enable Feature Records in Jira Next Gen

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

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 Mar 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!



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

105 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you