jira.permission.edit vs jira.issue.editable properties Edited

What is difference between jira.permission.edit and jira.issue.editable workflow properties?

Are there any difference for jira issue where set one or another of these properties?

2 answers

0 votes
Thomas Schlegel Community Champion Jan 18, 2018

Hi Alexey,

jira.issue.editable= true/false means, that the issue is editable

jira.permission.edit.group= <any jira group> means, that only users belonging to this group are able to edit the issue

Hi Thomas, thank you for your reply.

I need to restrict jira issue edit mode and I tried the following values:

1) Property: jira.permission.edit.denied

    Key: denied

2) Property: jira.issue.editable

    Key: false

So as I can see in 1st variant there is available "Attach files" option. In 2nd variant "Attach files" option is unavailable.

Are there any other differences in these cases?

Thomas Schlegel Community Champion Jan 19, 2018

I would always use "jira.issue.editable" if you want to prohibit editing issues completely in a certain workflow state. Before you mentioned it, I didn't even knew the property "jira.permission.edit.denied".  So, no, I don't know the differences between them. 

If you want to restrict editing to a group. e.g. administrators, I would use "jira.permission.edit.group".

Hello Thomas,

 

I am also trying to set my workflow with jira.permission...

 

Only a certain group should have permission to edit a workflow from a specific status onwards. Before that status everyone can work on the issue.

 

I tried all of your suggestions but none has worked for me.

 

Any idea what could be the problem? 

 

Thanks and best regards

0 votes
Joseph Pitt Community Champion May 02, 2018

You keep saying 'edit a workflow'. Do you really mean edit an issue AFTER a point in the workflow?

Hello @Joseph Pitt,

yes exactly.

 

Check this Workflow for example. It should give the permission only to Controlling Group from the transition "To Controlling"Workflow.png

You may want to try using conditions as well. That limits who can transition the issue (controller group), etc.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,516 views 15 20
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you