Default Scrum project has issue types "Story" AND "User Story" but why?

[Guido Santo]

JIRA Cloud:

When creating a new "Classic" Scrum project from scratch, the new issue type scheme that gets created with it has the issue types "Story" and "User Story" in it.

This doesn't seem to make sense and will cause a mess when people use them interchangeably as they are the same thing or not? Perhaps there is a reason for this someone can share?

See attached screenshots about the scheme and settings.

[Jack Brickey]

I’m guessing you are on cloud. I have not created a project recently on cloud so maybe this is something new. I agree that it seems redundant and unnecessary. With that said can you not simply remote the “User Story” once project is created? Regardless I would provide feedback to Atlassian on this via the feedback link.

[Guido Santo]

Thanks, Jack.

I am on Cloud and yes, I could just remove one or the other but I would like to know if there is a reason behind this default setup.

I'll contact Atlassian to clarify and will post here again.

[Guido Santo]

Problem was resolved with the help of Atlassian's support.

It turned out to be a specific problem on our instance and not a general bug.

Bottom line is that there is supposed to be only one issue type "Story" and the type "User Story" we had was a residual from some older project. After removing it all worked as expected again.