Hi everyone,

As rkrishna said a couple years ago, we are interested in simplifying this area of JIRA before we add more functionality. Layering permissions across individual transitions would make JIRA workflows an order of magnitude more complex. Our focus, as a product, is on making JIRA's workflow and permissioning model simpler. I do not expect us to implement this in the foreseeable future.

I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform

For some transitions we use specific groups to resctrict the permission,
e.g.:
Step Integrated

• Transition: Verify Issue
  Only users in group jira-testers can execute this transition.

i.e. we use roles and groups to define permissions.

You can implement this feature using 2 steps:

• create a group (or a role) that includes the members that hold this rights (e.g. "Promote Issues to Test").
• use SIL function userInGroup to write your transition condition like this:

if(userInGroup("Promote Issues to Test",currentUser())) 
   return true;
else
   return false;

Simple Issue Language is meant to simplify your special processsing in conditions, validators or post-functions.
The code above has the same behavior as requested, except it is only for the transition it is implemented for.

Give it a try here: https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.jjupin
or here http://jira-plugins.kepler-rominfo.com/x/product/id/3

Here is how you create a condition, validator or post-function: http://confluence.kepler-rominfo.com/display/JJUP20/Writing+Validators%2C+Postfunctions+and+Conditions

My use case is as follows. I'm trying to implement a mechanism to delegate issues to a group. So, I've created an Assigned Group custom field. Assignation to a group happens by a workflow transition. This transition clears the assignee, with the understanding that someone in the Assigned Group will pick up the ticket and then assign it to themselves. However, I don't want members in the Assigned Group to be necessarily able to assign the issue to another group. So, I need new permission, something like Delegate to Group that permissions the workflow, and it must be separate from the Assign Issues permission.

Thanks for the recent comments.

At this time we do not have any plans to add this feature to our roadmap over the next 12 months. Adding custom permissions to custom workflows would add another layer of complexity to the admin section. Right now we are working on simplifying this area before we add further functionality. If you are interested participating in this new project you might like to take a look at the following prototype plugin.

Sorry that we have not made any updates to this issue in such a long time.

Regards,
Roy Krishna
JIRA Product Management
roy at atlassian dot com

I would also like to hear the status of this feature. It's been a long time since anyone from Atlassian has commented!

Hi,
We are also having same requirement.Is there any update on this issue.
If you have a solution it will be helpful to us.
Thanks

Any updates on this issue, we could use this feature and not having it poses a risk that someone might act on a issue that they shouldn't be able to.

Hi! Jira is a great concept, but some impossible little features do this system inflexible and clumsy. I suggest that You working only with top voted issues. But a lot of issues with no top votes are important for us, and for another users. I'm your client - and I'm pay for support not top voted issues, but for my important issues.

Hi, when this necessary feature will be implemented?