Custom field configuration - why restrict project?

[Daniel Garcia]

Let's say I have an issuetype "Bug" that is used in 2 of my 10 projects (controlled by issuetype scheme). 

I want to add a new customfield and have it available for all bugs.

In my customfield configuration I select Bug as the only isuetype. Is there any benefit in also restricting project?

The benefit of leaving project global is next time I add bug to another project I don't have to think about updating the custom field configuration.

[Aaron Williams · Accepted solution]

Hey @Daniel Garcia 

One reason to restrict a custom field to a project is to ensure the data collected by that field is from one project only. This can make reporting from that field easier, especially if you have a large instance. You'd know where they field is used ensuring any data is related to that one project. 

Any changes to the that field would be limited to one project, meaning less chance of affecting other projects unintentionally. 

And locking a field to one project ensures it is only used for its intended purpose. I would say this though, a lot of the time it is not necessary. 

I hope this helps. 

Thanks

Aaron. 

[Daniel Garcia]

in the scenario I described above, would it make any difference to indexing time/size?

[Aaron Williams]

It would, if that field is locked down to one project, it would not get dragged into liberal JQL searches, dashboard reporting etc.

One field on its own might not be noticeable in terms of performance but if you have over 6000 custom fields (Like some instances I know of) it would certainly rack up the load. 

And it makes the project it's in more efficient as there is less config for that one field. 

Thanks