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; } } }

Restrict editing issue but allow editing of a single user picker field in 'People' section

Jennifer Roth_tg0ymg

How can I restrict users from editing an issue while allowing them to manage a custom user field in the People section of an issue?

Background:

My project is locked down. Only certain groups can see and edit all the tickets in it.

Anyone can create tickets and view them. But after a certain point in the workflow, these users with view access can no longer edit them.

I have a custom user picker field that gives view access to the people selected. I want them to be able to add or remove themselves from that field, but don't know how to lock the entire ticket while giving them edit privileges on the one field.

Thank you!

Accepted answers

All comments

Michael Yaroshefsky - Visor for Jira

Hey @Jennifer Roth as far as I'm aware to do this exactly as you state (configuring permissions at field levels) you'll need an admin app/plugin like secure custom fields for Jira (I'm not affiliated nor can recommend it from first hand experience, but it's worth taking a look to see if is has what you need).

There is a workaround you could also try and see if it does what you want: Try placing the field in question on a transition screen rather than within the issue itself. This way you can keep the issue locked for editing and allow users to select the people picker field on the transition screen.

Hope that helps

John Funk

Hi Jennifer - Welcome to the Atlassian Community!

How are you locking the entire issue? And at what point?

Jennifer Roth_tg0ymg

Thank you, John!

All tickets beyond the initial workflow state are locked down.
When tickets are created, an automation sets the Assignee field to be the same as the Reporter. In the permission scheme, Assignees have the Edit permission. When the Reporter submits the ticket, the status changes to 'Submitted for Review' and the ticket is automatically assigned to someone new. At that point, the Reporter loses their edit permissions.

But I need Reporters to be able to share the ticket with others who can view the ticket, add comments, and remove themselves from the list of shared users.

If I use issue-level security to give users access to view and comment on a ticket that is locked down, will they be able to add and remove themselves from the ticket?

What's the point?
Contract review requests can be created six months before the contract needs to be renewed. Reporters should be able to edit draft documents but we don't want them editing anything after the ticket has been submitted for review/assignment.

Drafting (=editable) > Submitted for Review (=locked) > (then locked at every status that follows)

Jennifer Roth_tg0ymg

Thank you! I'm looking for a workaround but this is still very helpful.

John Funk

Why not just add Reporter to the Edit permissions?

Jennifer Roth_tg0ymg

Because Reporters should be able to edit draft documents but we don't want them editing anything after the ticket has been submitted for review/assignment. Thanks, John.

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

jira

jira-data-center

data-center

issue-security

permissions