User having trouble giving another user permission to close a issue on a workflow

[Derrick Youngblood]

I noticed in the 5.2.7 version of JIRA there is a feature called Permission Helper where you can find out if someone has access to an issue or not. Since I’m having trouble with the FACES helpdesk not being able to close an issue in CDBS, I plugged in the fields and came up with the results below. I still don’t know why the workflow buttons to close the issue are not showing up for him but I now know for sure the Permissions Scheme is not the issue.

[Derrick Youngblood · Accepted solution]

this has been resolved with the answer Nic gave

Editing workflows is covered at https://confluence.atlassian.com/display/JIRA/Configuring+Workflow

[Nic Brough -Adaptavist-]

There's no picture of your results (this seems to happen to Answers a lot when trying to attach stuff, you're not alone...)

You need to have another look at both permissions AND your workflow. Permissions schemes are better thought of as a list of flags that don't really do anything about actions themselves. All actions in Jira are protected though - mostly by looking at the flags. For example, Jira doesn't think "they have edit permission so they can edit stuff", it thinks "this person is trying to edit. What does the code tell me to look at? Oh, if they have the edit flag, then let them do it".

In a lot of cases, like Edit, admin project, view workflows, etc, the permission is hard-coded, but for your workflow it is based entirely on Conditions. The really obvious condition is "user can only resolve an issue if they have the resolve flag in this project". But... you could do things like "user can only use the resolve transition if they've got the delete flag set in this project". Not really sane, but possible.

Basically, check the *conditions* on the workflow and you'll be able to work out why the user does or doesn't match them.

[Derrick Youngblood]

So you think I should check the permission scheme for the project or on the workflow?

[Nic Brough -Adaptavist-]

Both. You need to read the workflow conditions, probably in conjunction with the permission scheme. Start with the workflow though.

[Derrick Youngblood]

now do I check the workflow conditions in the workflow schemes...I have been trying to look there but I am not getting any where

[Nic Brough -Adaptavist-]

You need to be an admin and able to edit the workflows, so you can look at the full details.

[Nic Brough -Adaptavist-]

No, you don't need to change anything - you just need the right to edit workflows - then you can look at them in the list of workflows. You don't need to look at schemes (other than to work out what workflows apply to a project/issue)

[Derrick Youngblood]

to edit a scheme, you must first disassociate all projects from it.

[Derrick Youngblood]

ok I see the list of workflows now what do I do?

[Derrick Youngblood]

I'm the server admin but when I do edit workflows I get

[Nic Brough -Adaptavist-]

Click "steps" on the workflow you think is a problem, you'll get a text representation of it and you can then descend into the transitions to check their conditions.

[Derrick Youngblood]

ok let me see if I can do this and get back with you thanks lot for your help

[Derrick Youngblood]

I’d believe that except all workflows work as designed when the user is in the DEVELOPER group.

It’s when I try to use the override with the user in the Developer Role to restrict them to just their projects have I ran into this problem.

Very bizarre.

[Derrick Youngblood]

Open(1) In Progress(2) On Hold(4) Close(6) This is how one workflow looks that works Open(1)

In Progress(2)

Closed(3)

On Hold(4)

This one is the one that doesn't work does it have anything to do with what number the step is for example closed is the 3rd step but above its the last step?

[Derrick Youngblood]

I ask the user the same question and this was her reply:

[Nic Brough -Adaptavist-]

Step back - you've given us a list of transitions. The number in brackets is simply the unique id of the transition in the workflow definition, it doesn't really matter too much. What you need to do next is descend into the transitions and look at the "conditions" on them.

[Derrick Youngblood]

How do we do that?

[Nic Brough -Adaptavist-]

Click on them

[Nic Brough -Adaptavist-]

Editing workflows is covered at https://confluence.atlassian.com/display/JIRA/Configuring+Workflow

[Derrick Youngblood]

There is a condition for close how do we get rid of it?

[Derrick Youngblood]

this helped thanks