-
Suggestion
-
Resolution: Fixed
-
None
Would it be possible to expose a system configuration option that would enable an organization, if they choose, to enforce that any newly created custom field always be assigned a project-specific context and to automatically delete the global context?
This would never stop a custom field from being reused. You simply add another project-specific context.
But this would stop the sprawl of custom fields into field configurations across all projects in a Jira instance, and would lessen the probability that, with the creation of each new custom field, we necessarily make Jira slower for everyone.
Because unfortunately not every organization has a dedicated Jira admin or set of admins that force the reuse of custom fields and actively prevent or discourage their creation.
Atlassian Update – 29 Oct 2020
Hi everyone,
I am happy to announce that this suggestion will be released in Jira 8.14.0.
We will allow and encourage to specify a context upon custom field creation. This change should mitigate problems related to global custom fields.
Thank you,
Szymon Korytnicki,
Jira Server Developer
[JRASERVER-71297] Add Config Option To Require Every New Custom Field to Add a Context
| Remote Link | New: This issue links to "Page (Confluence)" [ 884506 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 512688 ] |
| Description |
Original:
Would it be possible to expose a system configuration option that would enable an organization, if they choose, to enforce that any newly created custom field always be assigned a project-specific context and to automatically delete the global context?
This would never stop a custom field from being reused. You simply add another project-specific context. But this would stop the sprawl of custom fields into field configurations across all projects in a Jira instance, and would lessen the probability that, with the creation of each new custom field, we necessarily make Jira slower for everyone. Because unfortunately not every organization has a dedicated Jira admin or set of admins that force the reuse of custom fields and actively prevent or discourage their creation. {panel:title=Atlassian Update – 29 Oct 2020|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#ffffff} Hi everyone, I am happy to announce that this suggestion will be released in Jira 8.14.0. Thank you, Szymon Korytnicki, Jira Server Developer {panel} |
New:
Would it be possible to expose a system configuration option that would enable an organization, if they choose, to enforce that any newly created custom field always be assigned a project-specific context and to automatically delete the global context?
This would never stop a custom field from being reused. You simply add another project-specific context. But this would stop the sprawl of custom fields into field configurations across all projects in a Jira instance, and would lessen the probability that, with the creation of each new custom field, we necessarily make Jira slower for everyone. Because unfortunately not every organization has a dedicated Jira admin or set of admins that force the reuse of custom fields and actively prevent or discourage their creation. {panel:title=Atlassian Update – 29 Oct 2020|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#ffffff} Hi everyone, I am happy to announce that this suggestion will be released in Jira 8.14.0. We will allow and encourage to specify a context upon custom field creation. This change should mitigate problems related to global custom fields. Thank you, Szymon Korytnicki, Jira Server Developer {panel} |
| Description |
Original:
Would it be possible to expose a system configuration option that would enable an organization, if they choose, to enforce that any newly created custom field always be assigned a project-specific context and to automatically delete the global context?
This would never stop a custom field from being reused. You simply add another project-specific context. But this would stop the sprawl of custom fields into field configurations across all projects in a Jira instance, and would lessen the probability that, with the creation of each new custom field, we necessarily make Jira slower for everyone. Because unfortunately not every organization has a dedicated Jira admin or set of admins that force the reuse of custom fields and actively prevent or discourage their creation. |
New:
Would it be possible to expose a system configuration option that would enable an organization, if they choose, to enforce that any newly created custom field always be assigned a project-specific context and to automatically delete the global context?
This would never stop a custom field from being reused. You simply add another project-specific context. But this would stop the sprawl of custom fields into field configurations across all projects in a Jira instance, and would lessen the probability that, with the creation of each new custom field, we necessarily make Jira slower for everyone. Because unfortunately not every organization has a dedicated Jira admin or set of admins that force the reuse of custom fields and actively prevent or discourage their creation. {panel:title=Atlassian Update – 29 Oct 2020|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#ffffff} Hi everyone, I am happy to announce that this suggestion will be released in Jira 8.14.0. Thank you, Szymon Korytnicki, Jira Server Developer {panel} |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| PM Reviewed | New: 29/Oct/2020 | |
| Status | Original: Gathering Interest [ 11772 ] | New: In Progress [ 3 ] |
| Fix Version/s | New: 8.14.0 [ 92899 ] |
| Assignee | New: Szymon Korytnicki [ 292ec441c8da ] |
That is fantastic news. Thank you for looking into this.