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

Permissions confusion wrt assigning issues.

NickW

I am confused about the ability to 'assign' an issue.

I have created a permissionschema in which only two groups can assign issues - namely teamleaders and productowners:

When I login in and look at an issue as a developer I see two 'assigned' buttons next to the workflow dropdown. When I click on these, the buttons disappear and are replaced by a resolved button and its status becaomes assigned to the project lead. - image attached

So if I am logged in as a member of the developer group why do I still have the ability to assign? Why are there two assign buttons?

NOTE ADDED: Sorted the two buttons.. the workflow had an identical transition assigning the bug which was hidden under the the first one... not sure how that happened!! Operator error I guess... doh!! The permission part of this question still stands though...

Many thanks

Nick

Accepted answers

Thomas Schlegel

Hi Nick,

the buttons are your workflow transitions, you have to look at your workflow to identify, why there are these buttons.

Among other things, "Assign isue" controls the visibility of the "Assign" Button on the left side of "Comment". This is not visible in your screenshot, so I think, the permission is set correctly.

What is your "Assigned" workflow-transition doing ? Is it really changing the assignee of the issue ? Or is it just called "Assigned" ?

Look at your workflow and I think you will find the answer to your question.

Cheers

Thomas

All comments

Thomas Schlegel

Hi Nick,

the buttons are your workflow transitions, you have to look at your workflow to identify, why there are these buttons.

Among other things, "Assign isue" controls the visibility of the "Assign" Button on the left side of "Comment". This is not visible in your screenshot, so I think, the permission is set correctly.

What is your "Assigned" workflow-transition doing ? Is it really changing the assignee of the issue ? Or is it just called "Assigned" ?

Look at your workflow and I think you will find the answer to your question.

Cheers

Thomas

NickW

Hi Thomas

Thanks for the reply. I spotted the duplicate transition - our posts must have crossed.

I remain confused though... The remaining button (which needs renaming to "assign" as that is what the transition is doing appears next to the workflow button as shown above (yes the resolved button should read resolve!!!). My expectation was that this would not be shown due to the settings in the permissionscheme but you seem to be saying otherwise? How would I stop the developer role/group being able to assign bugs?

thanks

Nick

Thomas Schlegel

Hi Nick,

the visibility of the workflow transition is not controlled by the permission out of the box. You have to set a workflow condition to the workflow transition.

Set a permission condition to the workflow transition (https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-Applyingconditionstotransitions) . Then, users without assign permissions should not see the workflow transition.

Cheers

Thomas

NickW

Hi Thomas,

Many thanks!! I now pretty much get the desired behaviour (as far as I have tested ;-) ).

So just to be clear (and sorry if this is getting painfull but I am a noobie at this)..

1. If a user has assign permissions, an assign button will appear to the left of the comment button (A) but this action is unrelated to the current issue state? So the issue can be in the assigned state but assignee can be changed?

2. If the work flow has a transition called assign this will appear in the workflow buttons block (B) clicking this button forces a state transition.

So....

Is it possible to remove/hide button A?

Is it possible to give them identical behaviour i.e. adhere to workflow?

thanks

Nick

Petra Goldstein

Same issue here. Two "Assign" buttons. One is by virtue of the flow we created, and the other is the built in "Assign" function to just assign the issue to someone, with no state transition.

It would be helpful if I could simply rename the built in "Assign" button to "Re-Assign". Then my flow could work as designed, where "Assigned" is one of the fist states, and the "reassign" can be used as needed. Atlassian is right to provide the functionality to assign in general, but since this is a very common "action" name associated with state transitions, should have provided some flexibilty around it.

Is it really not possible to rename this button?

Mike

Nic Brough -Adaptavist-

The button already has the right name, and if you rename it, you'll need something better than "re-assign", because it needs to cover both assignee A -> assignee B, AND unassigned -> assignee A.

If you use the translation function or edit the language files, the translation could leak into other places where it might make less sense.

I'm not sure that moving the assign functioninto the workflow as nothing more than an assign is "very common" - I've seen it and used it myself a few times, but I'd call it "infrequent" or "rare" mostly. And, of course, I've used different names, leaving "assign" for the standard function

Petra Goldstein

Thanks for your response.

The source of this is that we are doing a quick switchover to Jira (wher 'quick' is important), and in order to make the leap seamless for people, using the same workflow we had before, and will change later. We are moving from Bugzilla, where the default workflow there includes an 'Assigned' state near the beginning. The name of the transition I am giving it is 'Assign' (In bugzilla you simply change the state rather than perform an action). I'll look for another name for 'Assign' in the flow.

I'll add - we have probably seen very different workflows.

Thanks!

Mike

Welcome!

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

Quick Links

Find more posts tagged with

jira

permission

workflow