jira.permission.editable.xxx as Step Property

[Marco Colageo]

Hi Community,

I'm developing a workflow introducing custom editable rules when reaching specific statuses.

For istance, I would like that only a Project Role called "SPR Manager" is allowed to edit the issue which is in a 'For Review' Status.

I implemented something similar for the 'Closed' status, as follows:

jira.permission.editable.group = jira-administrators

This restricts the edit right to the Jira Administrators only. That works great!

So I tried the following property unsuccessfully:

jira.permission.editable.projectrole= SPR Manager

Then, I tried using the project role ID (retrieved form the URL of the Project Role edit page) unsuccessfully again...

jira.permission.editable.projectrole= 10103

Any suggestions?

Many Thanks

Marco

[Christian Czaia [Decadis AG] · Accepted solution]

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 Colageo]

Hi Christian,

I had already tried that. It did not work.

Cheers

[Jobin Kuruvilla [Adaptavist]]

@Christian Glad it is useful :)

[Jobin Kuruvilla [Adaptavist]]

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 Colageo]

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

[Christian Czaia [Decadis AG]]

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...

[Jobin Kuruvilla [Adaptavist]]

@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.

[Raju Adluru]

Jobin

thanks for j-tricks and help in forums

jira.permission.editable.projectrole and groups = xxx

above property and values are working only when user is not in a group, which is not added to Edit issue permission.

i have a scenario where user or group or role should not be able to edit only in one workflow status, in other status they should be able to edit.

can somebody help me with this, how to restrict a user/group/role from editing a issue in one status.

thanks

[Jobin Kuruvilla [Adaptavist]]

On the status, restrict the permission to a group or role where the user is not a member of!

[Raju Adluru]

Jobin

If i do that, that group is cant edit issue at all. but i want to restrict group only on that status, can we do this?

that group should be able to edit issue except in that status, for e.g, epic should be editable for a group, when epic is finalized, that group should not be able edit epic. can we retrict same group which has edit permission, not to edit in a status?

only allow admins to edit.

[Jobin Kuruvilla [Adaptavist]]

If you are using the workflow property only on that status, you should be able to edit everywhere else. Not sure why that is not working.

[Raju Adluru]

I have added workflow property on that status, it is not working, it is allowing other group users to edit the issue, who has edit issue permission.

[Michal Crkon]

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.

[Michal Crkon]

i solved the problem, finally. property key is jira-permission-edit.group and property value is jira-system-admin. Even now i created a new group xxx with 2 member. i added this group to permission scheme in edit issue. now only this group may change the issue when is closed. They do not need to be in admin position.

[Michal Crkon]

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

[Christian Czaia [Decadis AG]]

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

[Jobin Kuruvilla [Adaptavist]]

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

[Michal Crkon]

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

[Jobin Kuruvilla [Adaptavist]]

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

[Jobin Kuruvilla [Adaptavist]]

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

[Michal Crkon]

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

[Michal Crkon]

We had jira.issue.editable false by default.

[Jobin Kuruvilla [Adaptavist]]

I am sorry, by default I meant that it is true if that is not explicitly set ;) You can just remove it for example or set it to true as you did.