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

Create Issue: Change the Issue Type in the Create Issue Mask is not possible

Elke Perner

Hello everybody,

we have a big problem, if we want to create an Issue, we click on Create Issue and the mask appears. But if we want to change the default issue type to another issue type in the list, it's not possible.

The mask does always reset to the default issue type?

Is this maybe a known Bug of Jira Version 5 or is this a configuration fault by ourself?

Best Regards

Elke

Accepted answers

Nic Brough -Adaptavist-

It's not a bug, it's the way it's designed. You shouldn't be able to change issue type on Create - the whole point of the prompts you see before the main screen are for your users to select the right project and issue type.

The reason is simple - ALL the configuration is hung off the issue type. Jira has to know what issue type you want before it can even display the screen to ask you to enter details. Let alone the field configurations and mandatory fields, workflow, custom fields, relevant contexts for custom fields determining their possible contents, and so-on.

All comments

Nic Brough -Adaptavist-

Martin Buchleit1

That could not be valid. Why should there be a combobox to switch between projects and issue types at the dialog. It is possible to select another projects, but it is not possible to select any other issue type!

Nic Brough -Adaptavist-

It's a nice theory, but you do understand that the coding would be a nightmare? Every time a user changes and issue type on the create screen, you'd have to go back and re-build the entire screen, working out every field setup again. That's a lot of work for both developers and the browser, it's far more efficent to prompt the user for project and issue-type.

In a real life analogy, you decide you're going shopping for food. You go into the supermarket (the project) and head to the cheese counter (issue type). Then you change your mind and say "tea". You're now asking the supermarket to replace the entire cheese section in front of you with shelves containing tea - different brands, different prices, different products. Possible, but a lot of work, and it's far more easy for you to simply go to the tea aisle.

What I'm getting at is that the issue-type is structural and hence difficult to change on demand because of everything hanging off it.

Martin Buchleit1

Sure I understand - but at the point of view of usability this is a nightmare!!!

The user has a combobox which is enabled and he can select values but the change is not done.

Is it possible to lock/disable the combobox so that it is not possible to change the issue type?

The normal user will create 99% the default issue type. But we are in going into a preview with key users and they are going to try this change...

Martin Buchleit1

We were able to find some details:

if you press the create button, the validators avoid the creation of an issue.

Afterwards you can switch the issue type once.

Welcome!

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

Quick Links

Find more posts tagged with

jira