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 transition to certain users using properties?

Rosa M Fossi

Hello Community, I've browsed around and it seems that there is truly no way to limit a transition to a handful of disparate users. I've been provided a list of 5 users who can "Cancel" a ticket within one project. These users don't necessarily share a group or a role... and I don't really want to create a group just for these 5 for this ONE project $:\$

Has anyone had success using the jira.permissions.move.user Transition Property?

Accepted answers

Alexey Matveev

Hello,

jira.permission.move.user lets a user to move issue (change issue project or type). It has nothing to do with transitioning issue.

You would need to create a role and set the User is in Project Role condition.

All comments

Alexey Matveev

Hello,

jira.permission.move.user lets a user to move issue (change issue project or type). It has nothing to do with transitioning issue.

You would need to create a role and set the User is in Project Role condition.

Rosa M Fossi

jira.permission.move.user lets a user to move issue

That makes sense. I was citing that property from another post but now that I'm re-reading it, I think they were using that as an example. I also read somewhere in my searches that the "TRANSITION_ISSUE" property has long since been deprecated.

I did not want to use a Project Role because then I'm having to add users individually to the "People" section of project (unless I create a new Role "Cancelers", then create a new group, add users to group, add said group to People and assign it "Cancelers" Role).

I'm surprised that as granular as JIRA gets in the back end, there is no option for setting a condition for "single user". I have a feeling this scenario will come up (for me). At that point, we are left with: If I have a transition that should only be executed by user_x, then: create a new group > add user_x to it > add condition User is in Group <insert new group> to the transition. Or some version of that where we add it as a role.

ANYWAY~ forgive my rambling... I'm sort of typing out loud here trying to figure out the approach. I'm almost thinking it's worth the Role & Group approach since it gives "visibility" to the fact that there are workflow / transition restrictions. I appreciate your response!

Sadia Aslam

Same is the Scenario I'm facing.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software-cloud

jira-cloud

transition

workflow