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; } } }

Why change issue type always requires choose the new type twice?

Karlie Hu

When changing issue type using the issue type icon dropdown, I can select a new issue type directly from there, but in the next window this setting never get carried on, I always need to choose the new type again. Is there a reason for that? It is not a big issue but this simple action makes me feel stupid every time.

Accepted answers

John Funk

Hi Karlie - Welcome to the Atlassian Community!

Can you describe step-by-step what you are doing? Are you just doing an edit on the screen? Or are you doing a Move?

All comments

John Funk

Hi Karlie - Welcome to the Atlassian Community!

Can you describe step-by-step what you are doing? Are you just doing an edit on the screen? Or are you doing a Move?

Karlie Hu

Hi John, this is what I usually do:

Click on the issue from backlog so it opens up on the right side of the screen;
Hover over the issue type icon that appears right before the issue code, a tooltip "issueType - change issue type" will appear;
Click on this icon to open a drop down menu with a list of all the other issue types you can change it too.
The action above will redirect me to a "Move issue" page, on which I need to choose the new issue type again.
Follow the move issue steps shown on screen to complete the change.

I personally feel this can be more user-friendly if at step 4 above, system can remember my choice in that drop down menu mentioned in step 3, so I don't have to make the same action twice. However, I'm also curious if there's a constrain or some other reason that causes this behavior?

Thank you very much!

John Funk

I thought it might be something like that.

If you are changing the issue type to one that is linked to a different workflow than the current issue type is, then you must perform a Move.

If the issue type you are changing to uses the same workflow then it will just let you change it.

The tooltip is trying to translate that process for you. Why it doesn't copy over the one you selected to the Move, I don't know. You could actually submit that as a bug in my opinion.

Your other option is to just select Move from the 3 dot menu to begin with and bypass the tooltip. :-)

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software