Switching fields when changing issue type

[a.ciric]

I don't fully understand how field configuration schemes work. 

As far as i understood, the showed fields on my screen should change if i select a different issue type, while i create a new issue. 

But even after hours of try 'n error it just does not work. 

I already created different

Issue Type Screen Schemes, Field Configurations AND Schemes and Issue Type Schemes 

and so on!

HOWEVER: 

inside of the project settings, my two Issue-types show their correct field_configuration BUT the same "Screen"

What am i missing?

[Velizar Borisov · Accepted solution]

Hey there,

I will try to explain that the way I'm understanding it:

So, the first you have to know is what is a Screen. The screen represents the list of fields that are shown either on a issue operation or on a particular transition in the workflow. 

Next thing is Screen Scheme. The Screen Scheme describes what screen will be shown on different issue operation. The issue operations are 3 - creation , editing and viewing (N.B. in this schema there is no "closure" operation). Typically, you will select one screen for all the three operations, but if you like to see let's say a reduced list of fields on the creation step, you will need another Screen with that reduced list and associate it with the Create issue operation.

And the final thing is the Issue Type Screen Scheme. It only sounds that crazy but the name helps you to understand what is inside. It is just a mapping of Issue types and Screen Schemes. So this is the place where you say which Issue type from your project will have it's own Screen Scheme. This is the highst level of the screen organisation and it is mapped to the whole project, so projects work with Issue Type Screen Schemes, not with Screen Schemes. 

About the Field Configuration - this is the full list of fields which will be used in the whole project (no matter the issue type) and here you can setup which will be mandatory. But be careful, as this is a global setting for all operations and this means a value should be put in the field since the creation of the ticket. 

Hope I helped you, 

Velizar.

[a.ciric]

Thanks. After i had some closer looks into this whole thin i know understand it alot better :-)