only certain role can transition

[gil]

Dear experts - I have 2 questions for JIRA configuration:

1). How do I set up JIRA project such that, only user with certain project role can transition to next status. So for example, say now the current status is Open. Only users with Project Leads role can transition to next set of status (like Assigned, On Hold, Close), and no one else should be able to do so.

2). In addition to #1, only user with certain role can update the fields on the issue form and no other users. To clarify, only when the issue is in Open status, then user with Project Lead role can update the fields, and no other user. When issue is with other status, any user can edit.

Thanks.

[MinC]

For Question 1:

You can use the JIRA built-in condition: User Is In Project Role in the workflow to configure only certain project role can execute the transition. You can refer to the following documentation as a guideline: http://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-conditions

For Question 2:

You can try to install the JIRA Suite Utilities for the feature: User Is In Any Group Conditions but this will only involve that a user cannot see that transition unless they are in one (not all) of the specified groups. You can refer to the following documentation as a guideline: https://studio.plugins.atlassian.com/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Conditions

Field security level requires the Field Security Plugin (https://plugins.atlassian.com/plugin/details/23216) but it seems this does not involve with the workflow operations.

[Dawn Cooper]

Please advise and clarify. We use roles in multiple projects but want to know that the conditions and validators using those roles, are limited by project. So my question is, Do the 'User is in Project Role' and 'User in Any Role' different or do they essentially work the same limiting capability by project since the project roles are defined in the Summary for each project. I would like to know that 'User in Any Role' has a greater capability 

[Mageswari]

Any transition has three things that control it i.e. pre-requisites and post -transition results:

Conditions - Controls who can perform a transition, and under what circumstances
Validators - Check that any user-supplied input is valid before performing the transition
Post Functions - Carry out some processing immediately after a transition is executed

Answering your first question, for a specific transition - under conditions you can provide details like "User Is In Project Role " to ececute the transition. This will make sure your transition is executed by a person in this particular project role only.

Coming to Question 2. Control over fields to be updated by one user can be done using "Transition View" while creating the transition.
Let us assume that the issue is in Status 'OPEN' and has been assigned to 'Project Lead'; Assuming the next transition is 'ASSIGNED', on the click of the available work flow action - ASSIGNED, provide a screen (Transition View) to choose the assignee to whom the task has to be assigned to.
For example: Let it be 'Change Assignee' screen. Here since the current assignee is Project Lead and only that person is permitted to execute the transition 'Assigned', only he/she will be able to do the update of the new assignee to whom the issue is to be assigned next.

In all other status, control users viewing the issue using 'Security Level' and provide them Edit permission.
You can also refer to "Configuring workflow" in JIRA documention for more details.

Hope this is clear.

Mageswari.k.