nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA create issue screen is displaying wrong

Jurica Petricevic

When trying to realize one project, we first made our own Issue Types and after that we changed their names several times.

What happened? When we go to Create Issue the display of the Issue Type name is wrong. When it comes to settings there that Issue Type no longer even exists under that name. We just renamed it but the display is just wrong. Does anyone know what this is about?

Accepted answers

Jurica Petricevic

So, this helped me:

Go to Jira settings > Issues > Issue Type schemes > Edit the desired scheme > drag and drop affected Issue type somewhere up or down on the list and then save the configuration. The Issue type can now be moved to the original position if required.

It is an already known problem for which there is only workaround for now:

Jira Server and Data Center / JRASERVER-64106

All comments

Nic Brough -Adaptavist-

Could you show us the list of issue types in the issue type scheme for the project and what you get in the selection list on create?

Jurica Petricevic

Of course I can, I'll show you the pictures in a few moments.

Jurica Petricevic

John Funk

Hi Jurica - have you re-indexed since the name changes?

Jurica Petricevic

Not once but exactly three times since the last change.

Nic Brough -Adaptavist-

Hmm. Are you using issue name translations at all?

Jurica Petricevic

So, this helped me:

Go to Jira settings > Issues > Issue Type schemes > Edit the desired scheme > drag and drop affected Issue type somewhere up or down on the list and then save the configuration. The Issue type can now be moved to the original position if required.

It is an already known problem for which there is only workaround for now:

Jira Server and Data Center / JRASERVER-64106

Nic Brough -Adaptavist-

Ah, I see, it's a cache that needs flushing and Atlassian have forgotten to do that on issue rename.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server