Best Practice For Associating Custom Fields to Specific Projects and Issue Types

We have a JIRA instance with several projects and maybe 150 or so Custom Fields. What is the best way to associate these Custom Fields to specific projects and issue types?

From what I can tell, there are two ways to do it:

  1. Edit the custom field context, and limit it to just the projects and issue types that use the custom field. Then create a single screen for each project that contains all the possible custom fields that are used by the issue types in that project.
  2. Leave the custom field context to be global, and instead create screens and screen schemes for each project and issue type. Only place on the screen the fields that are associated with that project and issue type combination.

I've seen suggestions for both solutions. This link (step 7) recommends method 1, whereas this link and this link (step 4) recommend method 2.

We currently use method 1, but were thinking about trying to migrate to method 2. However, as I started to look into it, I ended up needed to create a screen and screen scheme for pretty much every project / issue type combination. There isn't much consistency as far as the grouping for project / issue type combinations that our custom fields need to be associated with. And all those screens and screen scheme started to get a little unwieldy.

Are there any recommendations or best practices on which of the two methods above should be used?

1 answer

1 accepted

1 vote
Accepted answer

For 1. approach creating a screen for each project is not necessary. "limit it to just the projects and issue types that use the custom field" should be enough. Simply create a screen, which contains all custom fields. The custom fields, for which no custom field context exist for the project and issue type are automatically hidden on the screen e.g. when you create or edit an issue.

I personally use 1. and because Atlassian itself advertices 1. in I would go this 1. Your second link, which recommends method 2 is mainly pointing to a bug in JIRA 5.1 with problems in using method 1. But it looks like this is solved (see last comment in

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,711 views 17 21
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you