permissions in workflow with transitions

[Jon]

I was trying to restrict some users from changing the status of an issue when its in a certain status but cant seem to get it to work. I added a condition that only people in a group can transition but the issue is the other person still cannot. I created a group and added him to it and gave the group the permission to change the status but it does come up on his jira. 

One thing I noticed is that when I look at this group under the user management page it still shows that it doesn't have access to the product or product administration. When I click on give access it only takes me to a list of all users and lets me select to revoke privleges which doesn't seem right. 

[Vasi]

Hey Jon,

It has been quite some time since you posted this question, but just wanted to check with it if it went well.

Based on your description it should be all working fine.

So here are several question in case you haven't figured that out yet:

1. When you say that other person still cannot transition, does it mean that transition button is missing? Is it missing for everyone? Or you can click transition button but it fails?

2. When it comes to groups under user management, it is fine that a group doesn't have a product access. It is expected that some groups won't.
The most important is that a user would have product access via another group.
So as long as user can access Jira issue, you can configure any group for transition conditions.

3. If it is still not fixed, could you please provide some screenshots of configuration you did? Workflow condition perhaps?

Thank you,
Vasily

[Jon]

hi vasily, not sure if it was the ideal way but we did find away to restrict the transitioning to certain users using workflow groups. 

another question we did have is if we could prohibit the transitioning of epics if they contain issues of certain statuses. for example our Epics get transitioned into the closed status however that is only if the issues linked to it are Not in the loaded statues and have to be in sailed or confirmed status. when we go to transition the epic if there is an issue in the loaded status we would get a message saying it is not able to be performed. 

We have cloud as well which has seemed to be the reason for a lot of limitations. 

[Vasi]

Hey Jon,

I've tried to test it with workflow condition "Sub-Task Blocking Condition", however it is not working for Epics.

I did a little bit more research and it seems that the only option in this case is to use add-on "Jira Misc Workflow Extentions":
https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions?hosting=cloud&tab=overview

This feature is implemented in the add-on and should work as you are describing.

Hope it helps!
Vasily
 

[Jon]

thanks for the help on this. I don't know if you know something they do not or maybe I didn't communicate it properly but they said they cannot do this right now. 

qte

unfortunately, none of this is currently offered by JMWE for Jira Cloud.
Atlassian just released support for Conditions and Validators provided by apps, so we will be able to release support for your first requirement (preventing Epic transition based on linked issues' statuses) in the near future (hopefully sometime next month).unqte

[Vasi]

Jon,

In this case your information must be more up-to-date.

I went through several different discussions and feature requests and all of them were pointing out to JMWE. However I haven't verified that completely. Apologies for that.

So in this case it seems that the only option is to wait for the release from JMWE.

Regards,
Vasily