Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Using non standard issue types in Advanced Roadmaps

I have a business group who wants to use a non standard issue type in the plan, called Feature.  What are the cons in using an issue type that is not standard? Limitations? If I add it to the project configuration, will it be as useful and beneficial as a e.g. a story (a standard issue type)? Any help on this will be appreciated! 

1 answer

1 accepted

0 votes
Answer accepted

There's no limitations or cons for having another issue type in a project.  The pros are usually quite simple - you can see at a glance what it is likely to contain without reading the detail.  If you create feature at the standard issue level (not a sub-task type), it will work the same as any other type at that level (assuming it is set to use all the same schemes)

Thank you! Is there anyway to make the issue type at the Epic level and not Story level?

No, the Epic issue type is a special case, a system thing and there's a lot of code in Jira that assumes there is only one type of issue to be used as an epic (also, do not rename Epic - Jira Software works ok if you do, but some apps break in very interesting ways.  This is likely to go away as part of the closer integration with Jira Align, but for now, don't rename it)

Thank you, Nic!

Hey @Nic Brough _Adaptavist_ , I wanted to follow up on this one.  What about creating a hierarchical level in between Epic and Story.  In SAFe, they have other "levels" such as Capability and Feature.  Is it possible to create a new Advanced Roadmaps/Portfolio hierarchy level above Story?

So, I'm going to avoid the main question there.

SAFe defines Epic as being at a different level to Jira's Epic.  Epics in SAFe are higher up.

Jira does not (yet) really allow you to rename Epics (you can, technically, but it breaks some stuff.  This is changing soon).  To match SAFe, you want to rename them as Features.

But.  Yes, you are right, Portfolio/Advanced Roadmaps do indeed add layers.  But not about story, they add them above Epics.

Like pbrown007 likes this
pbrown007 I'm New Here Jul 09, 2020

Thanks so much for your answer, Nic.  This was incredibly helpful.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: Keeping on top of your dependencies is a key part of ensuring project success....

119 views 2 6
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