Custom field context and screen configurations?

Sami Kontio

If there are, for example, fifty Jira projects that are using the same screen configuration (issue type screen scheme, screen scheme and screen). One of these projects would like to have custom field to be shown in their screen and none of the other projects need that field.

Is it better to create new screen configurations for that one project OR add that custom field to existing screen configuration and create field context that prevents field to be seen in any other projects?

Are there some performance issues in these different approaches?

And would it make any difference if there would be more projects that need some project specific needs at their screens?

Nic Brough -Adaptavist-

This depends entirely on what the new field is for - might there be a time when the other projects start to use it?

You will need a different field configuration, or screens, or field context.  Of these, the field context is the only one that might have a small performance gain - global fields slow the use of the index more than fields that are localised (but since Jira 8, the impact of global field context has been massively reduced, and you'll struggle to measure any difference by localising a single field)