nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Edit button permissions

James Lebron_k2nesx

Hello community!
What I want is not the permission of the edit button on the issue under the project level provided by Jira itself, what I want is to control the permission of the edit button of the issue according to the field value in a specific issue. Is this possible?

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Mostly, no, you can't do this. Access to edit an issue is controlled at a project level, it's not dependent on fields.

I say "mostly", because you can do it with one "field" - the issue Status (it is not really a field, and it's actually a front for a workflow step, but it is easier for most to see it as a simple field)

If you edit your workflow, you will find it has a load of status, and if you edit the step the status is associated with, you will find you can put "properties" on it. One property you can add is "disallow edit", so you can say "when issue is in this status, do not allow edit" (by group or role as well, so you can refine it to "do not allow anyone except the project admins to edit issues in this status".

But you can't do that for any other field.

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Mostly, no, you can't do this. Access to edit an issue is controlled at a project level, it's not dependent on fields.

But you can't do that for any other field.

James Lebron_k2nesx

Thank you for your reply.

I get the general idea of what you mean, but I still have some questions about how to do it exactly.

Do I add properties on States, or do I add properties on Transitions？

I realize that the names and values of the properties are my own, how can I make them editable based on project roles or users?

Nic Brough -Adaptavist-

You add the properties to steps (status are mapped to steps, there is a 1:1 relationship, so you could equally say you add properties to status)

See https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ for the basic docs on how to use t properties. You'll probably want to use the permissions ones - jira.permission.edit.group = mygroup for example.

James Lebron_k2nesx

Thank you very much.
I think I have figured out how to do it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server