How to have project role admin be only able to edit a status.

[Jeff Parnell]

Hi All. 

I had comb through responses on how to be able to have a specific status only edited by the project admin role. i have tried various properties methods including the common suggested: 

Property Key: Jira.issue.editable                                                   Property Value: False

Property Key: Jira.issue.editable.projectrole=10002                    Property Value: True

The above method and it permutation doesn't seem to work. 

Note: all status seem to be default editable in all our workflows. 

Any help would be appreciated. 

Thanks

[Michael Wohlgemuth · Accepted solution]

Hey @Jeff Parnell 

What do you mean when you say "edit a status"?

Assuming you want only project admins to use transitions from status a to status b, you should limit the transition to the admin project role in the workflow by utilizing conditions.

Apologies if i understood you wrong.

regards

[Jeff Parnell]

Sorry, that is a little confusing. What we mean is that we want only the project role "admin" group members to have the ability to edit an issue that is in a specific status in the workflow.  We do not want to prohibit transitions to a status. 

For example, if a issue was in the "made in error" status,  only the project role admin group should have the ability to edit the content of the issue, not anyone else.  Given what we have read, we should be able to do this by the properties function on a status in the workflow. However, the recommend properties listed in my initial request seems to not work. 

Hope this helps. 

[Michael Wohlgemuth]

Understood.

Does this article help? (You should be able to exchange jira.permission.edit.group.1 with  jira.permission.edit.projectrole.1)

regards

[Jeff Parnell]

Hi Michael 

This method doesn't seem to work. I have tried the below.

Attempt 1:

Property Key: jira.permission.edit.projectrole.Administrators

Property Value: Administrators

Outcome: could not connect to the issue

Attempt 2:

Property Key: jira.permission.edit.projectrole.Administrators

Property Value: True

Outcome: Everyone could edit

Attempt 3 (since edit is on for everyone for default in jira)

Property Key: jira.permission.edit.projectrole.Administrators

Property Valie: Adminsitrators

Property Key: Jira.permission.edit.Denied

Property Value: True

Outcome: no one could edit

Attempt 4

Property Key: jira.permission.edit.projectadmingroup

Property Value: projectadmingroup

Outcome: everyone could edit

Attempt 5

Property Key: jira.permission.edit.projectadmingroup

Property Value: true

Outcome: everyone could edit

Attempt 6

Property Key: jira.permission.edit.projectadmingroup

Property Value: projectadmingroup

Property Key: Jira.permission.edit.Denied

Property Value: True

Outcome: no one can edit

[Michael Wohlgemuth]

try:

Property Key: jira.permission.edit.projectrole.1

Property Value: ID_of_your_role

To get the id, navigate to Administration -> System -> Project Roles and hover over "Edit" on the desired role. It should show the id in the bottom left corner of your browser (where the target URL gets displayed)

regards

[Jeff Parnell]

Yes. This worked! I assumed due to the wording in step 1 "group.1" was filler for the custom group, my mistake. Thank you so much. Your help is very much appreciated. 

[Michael Wohlgemuth]

<3

If the answer turned out to be helpful, i would appreciate it if you could mark it as such so others can find it easier :)

have a great day!