How to move issue type from issue type scheme to another issue type scheme?

Question

Hi,

I want to move test issue type to the testing issue type scheme  in order to control test issues better. Currently, I have an issue type scheme, which has development and test related issue types in one bundle so thinking that for testing I need to adjust my own workflows, screens etc.

From some reason,  I'm unable to have issue type specific screens so I would like to set issue type specific screens. I have test screen, screen scheme, issue type with issue type scheme defined for the test, but still when I'm creating and viewing test issues I don't see fields shown in my test screen.

Is it because I have test issue type also in my "main" issue type scheme? Cannot remove issue type from there as there are existing issues so how to do this ?

Help appreciated.

Br, Jouni

Jouni Riimala · Answer

Thx, I actually came here to delete my post as I got it working so I just needed to add screen scheme to my test issue type... However your explanation is good so keeping it here for the future reference, have a good one.

Manne Kjærby - ProProces · Answer

Hi Jouni.

I'm not entirely sure I understand you problem by reading your text.

But could it be that the fields that is not showing doesn't have your test project included in your custom field contexts?

--

"Is it because I have test issue type also in my "main" issue type scheme? Cannot remove issue type from there as there are existing issues so how to do this ?" No

Walter Buggenhout · Answer

Hi @Jouni Riimala ,

Let me start by taking a small step back first ...

Schemes are just a concept needed to link pieces of configuration you manage centrally to a project so you can use them there. An issue type, a workflow, a screen, ... is created once and with a unique name in your central Jira admin section. You then use a scheme to create a set of these unique items that can be associated together to a project.

An issue type scheme (a set of available issue types) is a very important building block, because other parts of your configuration depend on it as well. An issue type can only be present in a project once (a project has 1 issue type scheme, and an issue type can only be in an issue type scheme once). So looking at a project, there is no such thing as a main issue type scheme and other issue type schemes.

Screens (and custom fields) are more complex, though. The screens you see in a project are linked to the issue types you already have there via additional layers:

* screens: a screen is nothing more or less than a set of custom fields
* screen schemes: a group of maximum 3 screens; 1 screen for every type of operation you can perform on an issue (you can create, view or edit issues and use different sets of fields for each operation)
* issue type screen schemes: links a screen scheme to an issue type in your project. For every issue type in your project, your issue type screen scheme defines the screen scheme to be used.

If you look at your project's Project Settings > Issues > Screens you will see the issue type screen scheme that is linked to your project. By expanding the sections on that page under each issue type, you will be able to also so the screen schemes and screens that form your project's screen configuration. Under your Test issue type, you should be able to find the screens being used.

If the fields you want to see are on those screens, they can still be hidden for a number of reasons:

* They may be hidden from the view users are using. On their screen, they can select fields and - if the fields are there - unhide them themselves;
* They may be hidden through the field configuration linked to your project. Yes, that's yet another element of the configuration. Check if you can find the field in there and make sure it's not set as hidden.
* Each custom field has one/more contexts that allow you to only make them show in certain projects or issue types. In Jira Admin, navigate to Issues > Custom fields. Search for the fields there and check the context(s) to make sure this is not the case.

Hope this helps!