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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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?

1 answer

0 votes

Hi,

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. 

https://support.atlassian.com/jira-cloud-administration/docs/associate-field-behavior-with-an-issue-type/

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you