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 Custom Field values for different projects?

Hi All

I have a custom field called "Request Type" which is a dropdown list contain values "Business, Process, Technology". Now a new project wants some different values. How can I achieve that? When I create a new Field Configuration, I can only change if it's Required or not, not the values.



3 answers

1 accepted

1 vote
Answer accepted

Hey Jirong,

This can be done easily when creating more than 1 field configuration scheme context (this is not a field configuration!).

  1. Go to Custom Fields page, find "Request Type" field and click on hog > Configure.
  2. Click on Edit Configuration (next to "Applicable contexts for scheme"), which has already the options you have chosen for that first project (Business, Process, Technology).
  3. Now make sure to that under "Choose applicable context" you have the relevant project/s selected.
  4. Click Modify.
  5. Now click on "Add new context", fill out the relevant fields and choose the new project that should have different fields.
  6. Click Add.
  7. You will find 2 configuration for same field now. Just click on Edit Options for the second configuration and insert the values you want there.

More info:



Thanks, Peter, I create a new Context for this custom field and it works.

I notice something else. I create a new context for the field "Person To Notify" to set some default values for a project A. It behaves like this: when I create a new issue, if by default the project A is selected in the new submit screen, the "Person to Notify" are populated with these default values. At this moment, if I change the project to B, these values are still there which is not right. If the project is set to Project B when the screen is launched, then change to A, these fields are not populated, this is not right. I notice the default project is always set to the last issue I submitted.

You only choice is to recreate a field named the same with new value. 

Thats correct. and it worked for me in past.

you need to define a new schema to handle this.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

375 views 1 3
Join discussion

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