Advice when creating a custom field

Question

Hi,

I have created a number of custom fields, where previously as well as associating with the screens for that project, I have also made applicable to certain projects.

As the number of projects increase and the requirement for additional fields, this becomes more time consuming.

Am I right in thinking as I have associated the field with specific projects, I can leave the applicable context as "Global context" (so applicable to all projects). I have completed a quick test and this seems to work, but just wanted to get some guidance first.

As we copy the project settings from a "master" template for each new project we create, I should no longer need to complete the manual changes for the custom fields (as it will already be associated with the screens)

Thanks

Mark Segall · Answer

if I leave the field as global context, this field will only be visible on projects where I have associated to that screen?

Correct. However, if you those fields need to be unavailable to projects not included in your shared configuration, you probably want to adjust the field configuration schemes of those projects as the fields can be added to screens or adjusted via bulk edit functionality.

Can you explain how i do the customisation referred to in your last paragraph?

In the same place where you manage the field context...

https://YOURINSTANCE.atlassian.net/secure/admin/ConfigureCustomField!default.jspa?customFieldId=xxxxx

You would add a new context, set the desired values and assign to the desired project(s) and/or issue type(s).

Matt Hine · Answer

Thanks Mark.

Just to check I have understood correctly, if I leave the field as global context, this field will only be visible on projects where I have associated to that screen? From the quick checks I have done, this looks to be the case.

Yes I am quite strict with the custom fields, so will often make projects share them and just amend the options list as you have suggested, I also try where I can to make the fields generic.

Can you explain how i do the customisation referred to in your last paragraph?

Thanks

Mark Segall · Answer

Hi @Matt Hine - Correct. Global context will ensure the custom field is available to every project and having projects leverage a shared configuration will ensure that each new project has the same settings.

Custom field contexts are quite powerful.  I've seen many Jira configurations where admins have simply created a new field because Project A requires pick list values of 1,2,3 and Project B requires picklist values of 4,5,6.  In that scenario, they could've avoided custom field sprawl by simply creating contexts on the same field which would've given the same end result without the overhead of yet another field.

So, you're on the right path, but know that if you do encounter a scenario where one project needs a little customization, you can create a custom context while still sharing the same underlying screen configuration as other projects.