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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

cannot add "Story" issue type to next-gen project

I am the main jira admin and I cannot add the standard issue type of "Story" to my next gen project.  It is available, but keeps throwing an error that does not help at all.


Screen Shot 2020-01-06 at 2.24.00 PM.png

1 answer

0 votes
Pavel V Atlassian Team Jan 06, 2020

Hello Jeremy!

Does the error appear on all issue types, or only Story? If you click "Create issue type" does that work?


all issue types including "create issue type"

Pavel V Atlassian Team Jan 07, 2020

This may or may not be related to a bug where reserved field names show the same error:

We are working on a fix. In the meantime, can you please take a look at your fields and see if any custom field has name that is used by Jira internally? Renaming should do the trick and allow you to create new issue types. (It is not necessary to delete fields. Rename is enough.)

Example: field Resolution will show error. Resolution2 will be fine.

I understand it is difficult to find out which fields are used internally; if you post your field names I can check if there is a conflict.

Please let me know if that worked.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events