Field configurations do not work

Question

Hello,

i have two issue types: A and B, and created separate field configurations for them. Also i have associated those field configurations via field configuration schemes to the two issue types.

The problem is, that whatever configuration i am making, the  default config seems to overrule them. Here is an example:

I have a custom field which is being used on a screen on both type A and type B issue types. But on type A i want to hide the field in the create screen, as i want the field to be filled later in the workflow. not at the start.

(my assumption is that all the fields which i want to use in the workflow later need to be in the create screen. otherwise they dont exist in the workflow later).

Now i have configured the field configuration, so that the field is hidden for type A and shown for type B. But it has zero effect. Only if i edit the default field configuration it has an effect. But thats not what i want to achieve.

Maybe i am missunderstanding the whole concept here....

Nic Brough -Adaptavist- · Accepted Answer

Field configurations hide fields completely, making their presence on screens irrelevant when hidden.

To answer the presented question, my best guess is that you have not applied the field configurations to the project (via the field configuration scheme association).

But the question inside the body is different.  You're trying to hide a field on create and then ask the user for it later in the process.  Field configurations don't do that, you need to be looking at the screens.  You need one screen for Create issue type A, and a second screen for Create issue type B.  The issue edit screen is probably the same for both types, and quite likely to be the same as "create issue B".  You might also want transition screens with the field on it.

Joe Pitt · Accepted Answer

@Josef Tufan Field configurations can customize how a field behaves for a particular issue TYPE in a specific Project.  For instance you can make a field required for one issue type, but not another in the same project by setting the field required and applying that configuration to one issue type in the field configuration scheme. The 'scheme' is made up of one or more field configurations for specific issue types. You can also have different text appear under a field for different issue types. See https://confluence.atlassian.com/adminjiracloud/issue-field-configurations-844500794.html