Allow Issues to have different field configurations

[Trena Norcia]

Atlassian PLEASE ANSWER THIS!  I have came across this same question multiple times and NONE have Been Answered?

https://community.atlassian.com/t5/Jira-questions/How-to-assign-Field-Configuration-Screen-scheme-to-the-JIRA/qaq-p/408642

We have multiple issue types and each one needs a different field configuration.  When the project is created it assigns all issue types to the default:

As you can see this is an issue when you need specific fields ONLY on certain issue types and to make them required:

We NEED absolutely NEED to have each issue assigned to a specific field configuration.  You can see we have created specific screen scheme for each and need the field configuration to be different as well.


Please help resolve this on going issue for us.  Your time and attention to this is greatly appreciated.

[Nic Brough -Adaptavist-]

I do not understand what you have been reading, because everything I can find has the same answer - use field configuration schemes as intended.

• As an admin,go to "field configurations" and add all the ones you need. 
• Then go to "field configuration schemes" and add a new one.
• Edit that one and associate each issue type with the "field configuration" you want it to have
• Go to the project and select the new "field configuration scheme"

[Trena Norcia]

I think the issue is that all issue types have been set as default when the project was configured. Right now we are using Epic, Bug and Task. 

They each need a different field configuration.  However when we try to change the FC scheme , it allows me to change Bug to the Bug field config:

However, when I try to change the task issue, it moves the bug issue type back to default:

This is the same issue that I am having and it is from 2014?  There are posts from other community users trying to help out but the issue is not resolved there are no posts from Atlassian and this is the same issue I am experiencing.  Thank you for reaching out and hopefully we can resolve this.

 https://community.atlassian.com/t5/Jira-questions/How-to-assign-Field-Configuration-Screen-scheme-to-the-JIRA/qaq-p/408642

[Nic Brough -Adaptavist-]

Ok, I think the project adminstration view is confusing things quite a lot here.

Please note that I am aware that that statement may be seen as condescending or arrogant.  It is not intended to be.  I have not been able to construct a way to say what I want in a good way without an over-long essay, which probably loses all the clarity as well as being a long read.

I do not thing the project administration stuff in Jira is very clear.  I know it needs to be complicated so that it can support the flexibility Jira has, but I think it could be done a lot better.

I hold that opinion because I fail to use it.  When I want to re-configure a project, I do start by going through project admin, and a lot of it works.  But with some of it, I really just get confused, and so I fall back on the global configuration.  I think because it is reductionist, and I'm mostly an Engineer from a family with a lot of Engineers, and reductionism helps us a lot.

So, I'd like to go back to my (reductionist) suggestion, but expand a little.

• Go to the project admin area and look at the name of the "field configuration scheme" it is currently using.  Just note that down, do not do anything with it
• Go to the global admin area for issues (cog at the top right, issues)
• Go to "field configurations" and check you have the ones you want to use (add more if you need)
• Then go to "field configuration schemes" and add a new one
• Edit that "field configuration scheme" and associate each issue type with the "field configuration" you want it to have
• Go to the project and select the new "field configuration scheme"

[Trena Norcia]

Nic, I appreciate your feedback and your working through this with me, allow me to show you where I am still failing with the steps you sent me. (if it helps, it is at the same point that I am failing with any suggestions sent to me)

• Go to the project admin area and look at the name of the "field configuration
  scheme" it is currently using.  Just note that down, do not do anything with it
  
• Go to the global admin area for issues (cog at the top right, issues)
• Go to "field configurations" and check you have the ones you want to use (add more if you need)
  
• Then go to "field configuration schemes" and add a new one

• Edit that "field configuration scheme" and associate each issue type with the "field configuration" you want it to have

BUG:

EPIC:

TASK:

• Go to the project and select the new "field configuration scheme"

Project uses the same FC scheme for the 3 issue types:

when I try to associate a issue type I am only allowed to change one the other 2 remain in default.  Change scheme for bug to bug fc scheme as you select a scheme then it is assigned to the issue ( I believe this is where the issue is?)



Shows Bug Issue with correct bug FC: other 2 issues types are still in default:

  If I attempt to change another it removes the prior one I change and sets it back to default change task to task FC: MOVES BUG back to default???

 

[Nic Brough -Adaptavist-]

Ok, third time lucky (my last two responses seem to have disappeared)

Your answers have explained what is wrong - I think you are mixing up field configurations with field configuration schemes.

When I said

• Then go to "field configuration schemes" and add a new one

you seem to have added three, and later when you are seeing "moves back to default", it's not doing that, you're actually looking at a different thing because you are swapping between them, not chaning field configurations.

So, roll back to that step and:

• Add one new field configuration scheme, and call it something obvious like "my new FCS"
• Confligure the new scheme, you should see it just says something like "default:  default field configuration"
• Add three lines to it by using "Associate an issue type with a field configuration" - once for each of your three issue types, and mapping the appropriate field configuration you showed above
• Now go back to the project admin and go for "fields".  Do not amend the body of this, use the "Actions" towards the top right and hit "use a different scheme" - from there select "my new FCS"
• After selecting the new scheme, you should return back to that screen, where you should see your three issue types listed as having different field configurations.

[Trudy Claspill]

I think I see where you went wrong.

A project can have only one "Field Configuration Scheme" associated with it.

Within a Field Configuration Scheme you can have multiple issue types. Each issue type gets associated with a Field Configuration.

Notice the difference - Field Configuration vs. Field Configuration Scheme.

Looking at the screens you provided for this step:

"Edit that "field configuration scheme" and associate each issue type with the "field configuration" you want it to have"

...what you did was create 3 Field Configuration Schemes; one for each type of issue. What you need to do is create ONE Field Configuration Scheme, and in it add each type of issue with its associated Field Configuration. You must also have a default Field Configuration defined in the Field Configuration Scheme. The default Field Configuration will be used for any issue type that is not otherwise explicitly called out in the Scheme to be associated with a particular Field Configuration.

Here's an example of a Field Configuration Scheme that serves different Field Configurations depending on the type of issue.

The Story issue type uses the "DEV: STORY Default Field Configuration" field configuration.

Any other issue type available in the project will use the "DEV: Default Field Configuration" field configuration.

To add more issue types and associate each one with a particular Field Configuration, click on the button in the upper right labeled "Associate an issue type with a field configuration". That will pop open a dialog where you select the issue type (i.e. Bug) and the Field Configuration to associate with that issue type.

Here I've added the Bug issue type

Once you have all the issue types you want and their associated field configuration, plus a Default field configuration, in your Field Configuration Scheme, then you go to your Project Settings, select Fields, and use the Action button to access the Use A Different Scheme option.

Through that you select the new Field Configuration Scheme you created.

[Trena Norcia]

Nic and Trudy  - Thank you for your help!!!!  Everything is great.  I posted this reply but did not see where took and I wanted to ensure gratitude for the great help.

[Jazz]

4 years later, I read this whole thread and it helped me fix the same issue Trena was having!! Thanks everyone! 

[Sachin]

Hello @Trena Norcia ,

I am not with Atlassian, but I am part of Atlassian Community just like you. I will try to help you.

As a jira admin

1. Goto Settings (cog) --> Issues --> Field COnfiguration Scheme --> Add field configuration Scheme

2. Goto Field configuration --> Add Field configuration (you can add as many as you like, in my case I have added three - story, bug and epic issyetypes)

3. Now come back Field configuration scheme (Step2) --> Click configure on your newly added field configuration scheme --> Associate an issuetype with a field configuration --> Associate an issuetype with a field configuration
Eg: Bug --> Field Configuration for Bug
4. Goto your project --> Project settings --> Fields --> Actions --> Use a different scheme --> Add your newly create field configuration scheme.


Best,
Sachin.

[Trena Norcia]

Thank you and those steps were so clearly defined.  The issue is that all our projects were created with the default field configuration.  Therefore following your steps changes all the issues types in that project to the selected new field scheme.  There is no way to just change the field configuration for just a specific issue type?  I truly hope Atlassian will answer as I have seen this same questions posted and sometimes with extremely negative remarks regarding the difficulty and lack of response from Atlassian surrounding this issue.

 Thank you for reaching out and your steps are perfect if the issue types were not all linked together to default.

[irina.korik]

@Trena Norcia

I have the same default config issue while adding custom fields for the specific issue type. I solved it by editing Applicable contexts for scheme. Listing the steps here in case it might still be helpful for you.

1. Go to your custom field and click context link in Screens and contexts column

2. Click Edit Configuration link next to Applicable contexts.

3. You will be able to pick and choose projects and issue types you want this custom field appear on.