Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to have different field configurations within a project?

Hi community,


I have a Project "Service Requests" and within that project I have different Issue types. 


Different Issue Types have different custom fields assigned to them. For some of the Issue types I want to have required fields that vary between types.


I have tried creating Field Configuration schemes and associating Issue Types to that, however in my Project all Issue Types are linked to the default.


Is it possible to use multiple Field Configuration schemes in one Project? If so, how do you set this up?

2 answers

The thread helped, thanks

0 votes


In your field configuration scheme you cap map field configuration to an issue type, you can have different field configuration in you field configuration scheme.

Can you make sur the you project is using the correct Field Configuration scheme.

Thanks Mohammed. So I've completed those steps before however in the Project I can only seem to choose one field configuration scheme, which is default. I want different configurations for different issue types within one Project. Is this possible please?Screenshot 2021-01-25 at 11.56.42.pngScreenshot 2021-01-25 at 11.58.34.png

You are confusing "field configurations" with "field configuration schemes" (a very easy mistake to make, I've never thought it was clear)

  • A "field configuration" is a list of all the fields, with flags to set their behaviour.
  • A "field configuration scheme" is a list of all the issue types, which tells a project which "field configuration" to use for each issue type in it

You only need one field configuration scheme, but that scheme can point to many field configurations. 

The minimal example is you create two field configurations; let's call them "FC - bugs" and "FC - everything else".  Set the flags you need for your different acting fields in those two.  Then create a field configuratin scheme (FCS), and tell it "by default, use 'FC - everything else' but for Bugs, use 'FC - bugs'".  Associate that with your project, and you'll find most of your issues behave in one way, and bugs are different.

Thank you! That makes total sense, have finally worked it out. Appreciate it

Hello @Nic Brough -Adaptavist- , 
thanks for your response it was helpful. 

But i m still facing an issue. 
So what I've done: 
I've created Field Scheme
Created new Field Configuraiton where i set the behavior i want
Associated the project with that Field Scheme 
More specifically: "Description" Field to be required for screen 1,2
And "Desc" field to be required for screen 3
While trying to create a task using screen 3, I get an error saying that Description is a mandatory field. 

Can you please advise? Ay idea of what I may be doing wrong? 

Thanks in advance, 

Hi Maria,

I am not sure what you mean by "field scheme", but there's a deeper problem - you are guessing that Jira does "field on screen can be mandatory" via the field configurations.

This is the wrong assumption, it does not.

When you flag a field as mandatory in a field configuration, then the field is mandatory on the project/issuetype the field configuration applies to.  Screens are irrelevant, the field must be filled when you create an issue, and you cannot blank it out during an edit or transition.

Hello @Nic Brough -Adaptavist- ,

Thanks for getting back to me. 

By "field scheme" i mean Field Configuration Scheme. 

So From what I can understand here, Per project we have issue type, for each issue type we have a specific Field configuration that applies to and a screen that is associated with that issue type: (Project > Settings > Issue types) as shown below: 

issue types.PNG

Question is :
How can i set different Field configurations per issue type? 

So for example :
I want for bug (issue type) to have Field configuration A
but for Story (issue type) i want to have Field configuration B



That is what the field configuration scheme does - it tells the project which field configuration to use for each issue type.

@Nic Brough -Adaptavist- 

Question is :
How can i set different Field configurations per issue type? 

You use a field configuration scheme.  They tell the project which field configuration to use for an issue type a project.

@Nic Brough -Adaptavist- 

I want to have different issue types with different field configurations.

1. is this supported from jira ? 
1.a. Can you please guide me on how this can be achieved? (step by step )



I do not know how else to say that you use a field configuration screen - create a new one, edit an existing one, or copy one.  Then change it to tell the project what field configuration each issue type will use.

I guess you mean field configuration Scheme and not screen. 

I understand the theory, what i need to know is the "Then change" part... HOW i will set field configuration for each issue type ... the steps i need to follow on jira.. on which page screen i need to go etc.
I think you don't get my question. But aw thanks for trying to help :) 

Yes, I miskeyed when I repeated it for the third time.

The steps, to do it from scratch are what I've said already - create (or copy) a new field configuration scheme, set up the mapping for each issue type (it will always have a default one), then tell your project to use your new scheme.

I'm not going to try to walk you through every step, it's not going to help you learn.  Best thing to do is actually try it - click "create" in the field configuration scheme list and look at what Jira puts in front of you, reading all the options for the ones you want.

Thanks for explaining the theory I already knew :) 

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events