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:
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?
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 http://blogs.atlassian.com/2013/12/8-steps-to-jira-field-greatness/ 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 https://jira.atlassian.com/browse/JRA-29310).
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...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG