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

When issue type is changed request type is nulled

František Vůjtek

Hello There, im having issue when im changing issue type from Incident to Task, my screen will change the sorting of fields and request type field is nulled.

Im sending screens before and after changing the issue types. Both of them have same screen settings.

Do you know by an chance, why is this happening?

Accepted answers

Walter Buggenhout

Hi @František Vůjtek,

Yes. A request type is linked to an issue type. So if you change the issue type of an issue, the previously selected request type is no longer valid and it is cleared.

Similarly, screens and workflows are linked to issue types as well. If you see the order of screens being updated, that is because a different screen configuration and layout is being applied.

Hope this clarifies!

All comments

Walter Buggenhout

Hi @František Vůjtek,

Yes. A request type is linked to an issue type. So if you change the issue type of an issue, the previously selected request type is no longer valid and it is cleared.

Similarly, screens and workflows are linked to issue types as well. If you see the order of screens being updated, that is because a different screen configuration and layout is being applied.

Hope this clarifies!

František Vůjtek

Oh ok i get it. And what about the layout or screen settings?

Why after issue type has been changed there is different sorting for the fields? Where i can set it to be same for all issue types?

Walter Buggenhout

As I mentioned, @František Vůjtek: the layout of screens is also linked to your issue types. If you change the issue type of an issue, you will see the screen layout that is linked to the new issue type. If that is not the same as the old one, you will see a lot of stuff being rearranged.

Basically, if you notice the issue type of an issue is wrong, don't update the issue type on screen, but use the move issue function to do this in a controlled manner. See this support article to learn more about how that works.

Walter Buggenhout

How you can set the same screen configuration and lay-out for all issue types is different between company-managed and team-managed projects.

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

jira-software-cloud