Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to change assignee permission to be set per column

Melanie Whyte
Contributor
September 28, 2021

Hi,

Is there a way to allow a user group to change the assignee of an issue only once the issue has moved to certain lanes in the Kanban?

I have a development board where 'help team' users can create issues to be looked at. When they create the ticket it goes into column 1 (to-do) and they are not allowed to assign the issue to a developer.  Only the 'developers group' can assign tickets

Once a developer takes the ticket they will progress it through the remaining kanban lanes, at this point they may re-assign it to a member of the help team group for more info.  

Is there a way that customer team group can re-assign to the developer when they reply... without them being able to assign the issue in the 'to-do' column?

Thanks

M

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 4, 2021

Yes, but it is a bit convoluted and needs some design and planning.

Also, it's not done with the board.  A board is a view of a selection of issues.  Each column in the board is a collection of status (often a single status), so you need to start by looking at the board config to establish which status makes an issue be in a column.

Who can assign an issue is determined by the permissions in the project the issue is in.  So, your second step is to look at all the permissions for all the projects mentioned in the board.  Here, you want to make sure that everyone who should be able to assign issues does have the permission.  This is NOT related to the columns yet, you're just granting permission to assign issues for everyone who should have it at any time.

So, the trick now is to understand that because a column is actually a status (or several status) in a workflow, you can impose other permissions/denials on the column by applying them to status in the workflow settings.

So, let's imagine the most simple config you might have for your question. 

You have a board that has several columns, all with 1:1 mappings with status in your workflow, so column:new has just the to-do status in it, and later in the process, you have a column:we're-working-on-it that contains the status in-progress.

First, set the permissions in the project so that the groups 'developers' and 'help team' can assign issues

Second, edit the workflow, and look at the to-do status.  Go to the "properties" tab and add a new property to it: jira.permission.assign.group=developers -

This should limit the assigners to just the developers group, while the issue is in to-do

You might want to get even more clever and use the "assignee" property as well, which could limit the reassign to only developers or helpers, depending on status!

See https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status for a proper write-up of how this stuff works

Melanie Whyte
Contributor
November 2, 2021

Hi Nic,

Sorry for the delayed response, i didn't get an email notification. 

This is exactly what i was looking for and it worked.  Thank you very much for your step by step help :)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events