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

Limit which Jira user groups can edit certain (but not all) custom fields in an Issue Type ticket

Jatin Patel_d7psqq

I have a Project which contains multiple user groups and lots of Issue Types. In the Permissions Scheme, all user groups have the ability to "Edit Issues" and this works fine for all Issue Types apart from one.

For this exception "Issue Type ABC", I want to create a rule so that anyone can create an ticket, but only members of user group "CF-MNO PQR" can edit certain custom fields within the ticket. For example after a ticket has been created, anyone can edit custom field 'description', however, only members of group "CF-MNO PQR" can edit 'Assignee' or 'Priority'.

I have created a Board and set transitions so only user group "CF-MNO PQR" can move the ticket through the various statuses. However, this doesn't stop all users from being able to edit the ticket.

I have investigated Property Key and Property Value. I have tried Property Key jira.permission.edit.group & Property Value CF-MNO PQR at each workflow status, and this allows only members of that group to edit the ticket. However, this means other users cannot update custom fields such as 'description' which is not what I want.

Does anyone have any advice on how to solve this problem?

Thanks! Jatin

Accepted answers

All comments

Mikael Sandberg

You would need an app in order to do field security, Jira out-of-the-box does not support that, unless you add the fields to a transition screen and only allow specific groups to use that transition.

Joseph Chung Yin

@Jatin Patel -

To supplement what @Mikael Sandberg suggestion regarding to transition screen, it means that you control the population of those fields via the WF where you can add in conditions for the transition controlling who can execute the transition via the WF. So if it is implemented, then any user who is failed the condition checks, he/she will not even see the WF buttons in the issue operation.

Furthermore, this also meaning that those fields need to be available only in the issue view screen (thus read-only). Population or editing of those fields are controlled completely via the WF transition events.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Jatin Patel_d7psqq

Thanks for the response @Mikael Sandberg

Jatin Patel_d7psqq

Thanks for the further explanation @Joseph Chung Yin

So if i understand correctly, I remove the questions that I want limited (Priority & Assignee) from the "Edit Screen". Then I add those to the transitions. And on the transitions, keep the condition so that only one user group can make them.

However, if I want to change the priority/assignee yet am not in a position to make a transition, then how would you suggest that I go about doing that?

In the image below, I have shown part of my current workflow. I have created a transition from "Assigned" to "Assigned", and created a transition screen for that. However, when I try to move a ticket on the Board from Assigned, the only option available is "In Progress". When I drop the ticket back in "Assigned", the transition screen I created does not show up.

Joseph Chung Yin

@Jatin Patel -

To answer your 1st question, there is no work around since WF is now driving the control.

In regards to your second question, I believe your WF setup + board column setup may be mis-configured. Can you provide your WF status mappings to your board columns + your transition condition configuration?

Best, Joseph

Jatin Patel_d7psqq

@Joseph Chung Yin Thanks for offering to help and apologies for the delay.

Attached are three images

1. WF statuses

2. 'Board Column Management' to show WF status mappings to my board columns

3. Transition condition configuration - I've shared the configuration for the transition that goes from "assigned" to "assigned" (one condition that only 1 user group can move tickets)

Be very good to get your thoughts on how users can change the priority/assignee without making a transition, if those questions only exist on a transition screen.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server