Permissions - Can you define Issue schemas and/ or add custom fields at the Project level of permissioning?

[Beth Schaefermann]

As long as I am getting my "big hairy" questions out of the way today, I have one more. I have yet to figure out project-level permissioning for custom tracker schemas or the ability to add a custom field only at the project level.

I believe I understand how this works at the Jira Admin level, and I fear that this is not possible at the project level. I don't necessarily want all PMs across the enterprise to interact with Jira Admin, given the complexity and opportunity for chaos. Ideally, PMs could administer Issue definition specific to their project, adding custom fields to default Issue schemas and creating custom Issue schemas if desired.

Is the only way to do this at the Jira Admin level of permissions? Is there a plug-in for addressing this permissioning need?

If it doesn't exist, I see three options:

(1) Provide training and governance and allow PMs into Jira Admin (not ideal and high risk)

(2) Create a separate Jira instance per client (still requires significant training and heavy maintenance investment)

(3) Create a process for customization requests to global schemas (heavy overhead)

How are others approaching permissions and Issue schema customization who may be using Jira across an enterprise?

[Markus Lepper · Accepted solution]

Hi Beth,

Creating customer fields, assigning them to specific projects and screens is only possible by persons with admin rights; unfortunately!

Option 1 is too risky and project leads are not at all interested in this "bloody" tool/admin tasks butleading their team and do implentation work. They (will) refuse to learn the administration "just" to add some fields.

Option 2 not feasible due to heavy maintenance work needed. Just think of aligning company wide default setting among x Jira instances...will be a nightmare

=> So only option 3 is "possible". It's not the best solution one could think of, but...

We have defined an admin/IT-task with which project leads could request new custome fields (and their type, options, default values,...) for their projects or global usage.

Our admin team then implements these requests, touching lot of Jira admin areas (schemes, settings, fields, screens,...)

BR, Markus

[Beth Schaefermann]

Thanks, Markus - much appreciated. I think we are also going to try out the following and see if it works for us:

Jira's Project Specific Select Field -- Appears to be free; compatible with Jira 4.43 (Emailing Holger to see if their is an intent to upgrade to 4.4.)

Holger: "I don't see a reason, why the plugin should not work in JIRA 4.4. Just give it a try. (If you test the plugin, please have an extra look at XML backup and XML import, because I did not check this during the plugin development.) I am happy to hear, that the plugin is useful for you. If you consider to use it, please think about, how you can contribute to the plugin development as I am not able to take up support or feature requests on my own. To jump into JIRA plugin development is quite easy with the Atlassian SDK. Also the JIRA Project Specific Select Field Plug-in consists only of few java classes and velocity templates."

Potentially solves problem of customizing issues at the project level instead of at the Jira Admin level
https://plugins.atlassian.com/plugin/details/43950

[Beth Schaefermann]

I should have added that I will come back and post here with any info regarding whether it helped with our needs or no.