Why aren't the workflow properties working?

[James Shablow]

I am running JIRA 7.11. I have the following workflow: Open-->Incomplete-->In Peer Review-->In QA Review-->Closed.

- Only QA and admins have permission to close. This hasn't stopped a normal user from being able to close problems for some reason...
- Only administrators and current assignees should be able to resolve issues.
- Anyone can transition issues.

I am trying to do the following:
- Prevent everyone from editing an issue after it is passed the Incomplete stage.
- Allow anyone but the reported be assigned the task for the Peer Review stage.
- Allow only QA to be assigned the task for the QA Review stage.

I have tried the following properties (and variations of them), and they either break the functionality or don't do anything:

jira.issue.editable               false
jira.permission.edit.reporter     false
jira.permission.resolve.reporter  false
jira.permission.assign.lead       true
jira.permission.assignable.group  QA

Any advice would be greatly appreciated, as I cannot find detailed information anywhere. The most specific information I've been able to find is here, but is hasn't worked as I thought it would.

[Victor Mutambuki]

James,

jira.permission.edit.reporter - 

Step (usage: only to restrict permission to either roles,group, or users when issue is in that step). Example, jira.permission.edit.group=jira-administrators

Documentation indicates you choose ROLES, GROUPS or USERS

jira.issue.editable               false

This one should be okay

Victor

[James Shablow]

Thank you for the response Victor. The problem is, I could find nothing in documentation that describes how to use roles. Using groups and users is somewhat intuitive. 

I got it working partially though.

For the In QA Review properties, it put the following and that seems to be working for the most part now:

jira.permission.edit.group.1     jira-administrators
jira.permisison.edit.group.2     QA
jira.premission.assignable.group QA

Reporters can still assign the work to themselves and do things they should not be able to though, and I cannot find anything online with suggestions on how to alter this.

I would like the ability to prevent the reporter from doing anything after the Complete stage. Something like:

jira.permission.edit.reporter false
or 
jira.permission.assignable.reporter false

I tried to accomplish this with the following, but the reporter is still able to assign to themselves or click "Assign to me" to take over it.

jira.permission.edit.group jira-administrators
jira.permission.edit.lead  true

Any suggestions?

[Victor Mutambuki]

James,

Check your permission scheme to make sure that reporter doesn't have ability to edit.

Victor

[James Shablow]

Editing issues is permitted to QA, admins, the lead, and the assignee.

If if someone isn't the assignee, they have permission to assign the issue to themselves. If I remove the ability to assign to people, then JIRA doesn't let them assign it to someone else upon completing the issue. The idea is that they will have to assign it to another person (project lead by default), since the point is for it to enter review.

[Victor Mutambuki]

James,

To be able to have tickets assigned  to you, you must have the Assignable User Project permission.

victor

[James Shablow]

How would I allow the user to be assigned tasks anywhere if they weren't listed under assignable user? There are only three of us, so we will frequently be reviewing each other's work.

I see how this would be easy if it were always the same people performing the same tasks.

Maybe this isn't even a feature of Jira?