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

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.

Accepted answers

Derrick Youngblood

this has been resolved with the answer Nic gave

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

All comments

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

Derrick Youngblood

this has been resolved with the answer Nic gave

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

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud