jira.permission.editable.xxx as Step Property

Try: jira.permission.edit.projectrole = 10103

BTW @jobin, this is one of the most valuable pages for JIRA admins... Thx Jobin!

----

BTW: I'd put that property on every "final" workflow step (instead of jira.issue.editable = false / JIRA default)

jira.permission.edit.group = jira-administrators

That way an admin can still perform bulk-updates on "closed" issues :-)

All comments

You will have to use the id only. Can you make sure the project role had Edit permissions before you limited it in the Closed state?

If the role is not already in the permission schemes, this wouldn't work. Also see http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html

Marco Colageo1

Hi Jobin,

thanks for your reply.

The edit right is assigned through the Permission Scheme to:

- Reporter
- Current Assignee
- Administrators (project role)

Then, at project level I customise the 'SPR Manager' project role adding two users, which are not necessarily the Reporter, the Assignee nor an Administrator.

I would expect the...

jira.permission.editable.projectrole= 10103

...giving the 'super-edit-power' to those two users.

Is that feasible somehow?

Cheers

Marco

Try: jira.permission.edit.projectrole = 10103

BTW @jobin, this is one of the most valuable pages for JIRA admins... Thx Jobin!

----

BTW: I'd put that property on every "final" workflow step (instead of jira.issue.editable = false / JIRA default)

jira.permission.edit.group = jira-administrators

That way an admin can still perform bulk-updates on "closed" issues :-)

Marco Colageo1

Hi Christian,

I had already tried that. It did not work.

Cheers

AFAIK the edit permission is the ground level permission. So people in your SPR Manager role can only edit the issue if they are either reporter, assignee or administrator...

@Christian Glad it is useful

@foxiceit You cannot do this. You should have the project role 'SPR Manager' in the permission scheme. You can add/remove users from it at any time but the restriction will work only if it was there originally.

In short, you can restrict permissions but cannot grant new permissions.

hi guys,

i am trying to make close issue editable with permission for administrator. I tried http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html and also jira.permission.edit.group = jira-system-administrators with granted. I am getting errors says :

Error rendering 'com.atlassian.jira.jira-view-issue-plugin:details-module'. Please contact your JIRA administrators.

all my tries :

Property keyProperty value

jira.permission.edit.group = jira-system-administratorsgranted

jira.permission.edit.projectrole=10002

jira.permission.edit.projectrole=10002granted and true also

jira.issue.editable.users = emiccrkgranted and true also

I am getting above error msg or it is editable for everyone.

my permission scheme for edit issue is

Project Lead
Project Role (Administrators)
Project Role (Project Managers)
Project Role (Developers)
Project Role (Reporters)
Can someone help me? thanks. Miso

Just try jira.permission.edit.group = jira-system-administrators. Make sure they could edit before as well.

jira.issue.editable should be true by default. No need to give that explicitly.

It is working but it needs to keep both lines of permission:

jira.permission.edit.group = jira-system-administrators with no property value

jira.issue.editable with property value true

always i tried only one of them or crazy combinations. Thanks a million, Miso

Guys, it is strange. When i run this on test environment i have no problem, everything goes like from the book. But if i put the same changes to the live environment i am getting the same error: *Error rendering 'com.atlassian.jira.jira-view-issue-plugin:details-module'. Please contact your JIRA administrators.* What is going on? Does someone know how to fix it? I am trying to play with this and problem seems to be in the line *jira.permission.edit.group = jira-system-administrators * Thanks for any help. Miso

Do you have the "jira-system-administrators" group in your production environment and / or are you part of it?

Yes, there is this group and i am part of it. I tried also jira.permission.edit.user = EMICCRK with true/granted or without with the same result. Of course I added extra my name to the permission scheme for editing.

Look in the log files. I am guessing there is a plugin that is blown up when there is a permission issue.