Specific (edit) permissions for a specific issuetype

[Dirk Ronsmans]

I have a servicedesk project with the typical issue types:

Incident, Service Request, Problem and Change.

Overall there is no issue as to who can change something with Incident & Service Request as this is handled by the same team.

However, for Problem and Change we would like to block the edit permissions for all users except a select few (problem & change managers).

As JIRA doesn't have the ability to set "per issue type permissions" and are not planning on implementing it I'm looking for a workarround.

My initial plan is/was to set up the edit permissions with a custom group field and populate the field at creation time with the groups that should have edit permissions anyway.

That way I can leave out the normal teams in Change & Problem and leave everyone in at Incident & SR.

That would however mean I have to retro-activly change this on the older issues and remove the regular groups from the permissions so they don't automatically get access to change/problem (and then auto add them on incident/service request so they have permissions there)

Hence my search for advice, is anybody implementing this within the same project or has some good ideas on how to do this with minimal impact?

Or should this be moved to a disussion so we can search for a good workarround?

[Avinash Bhagawati {Appfire} · Accepted solution]

Hi @Dirk Ronsmans ,

Create an individual workflow for Problem and Change Issue type and add below property to each status of the workflow.

jira.permission.edit.group=jira-administrators 

With above property the issue is only edited by Jira administrators and the property needs to be added to each status of workflow.

Please refer the below knowledge document for how to implement this configuration.

https://confluence.atlassian.com/jirakb/how-to-limit-editing-permission-to-certain-groups-for-a-particular-issue-status-802171723.html

Thanks,

Avinash

[Dirk Ronsmans]

@Avinash Bhagawati {Appfire} 

Looks to be working!

Nice workarround but too bad it isn't something built in into the permission scheme :)

You wouldn't happen to know a similar workarround but then limiting only specific fields?

[Avinash Bhagawati {Appfire}]

Hi @Dirk Ronsmans ,

Unfortunately there is no configuration available for specific fields by default and you need to have app called script runner for Jira to configure this.

Thanks,

Avinash

[Dirk Ronsmans]

Great :)

I'll use their behaviours then!