Issue Security Levels to have Everyone View; Some Individuals Edit certain Issue Types

[S]

I have a few different Issue Types in my Project.  In the same Project, I want to make:

• Issue Type 1: Viewable to jira-software-users; Editable to jira-administrators only
• Issue Type 2, 3... n: Editable to all jira-software-users

I'm having trouble getting my head around how to combine the Project Edit Issue permission and Issue Security Levels to achieve this.  When I do it, Issue Type 1 disappears entirely for jira-software-users in the Sprint View, which I don't want.  Any help would be greatly appreciated.

We generally let everyone edit all Issue Types at our organization and we want to keep to that as much as possible.  We've been having problems with one specific Issue Type and we want to lock it down further (especially the Description and all the fields, not concerned with the Comments).  Only the proper content originators should be able to Edit the issue and change its Status (I got this down), but retain Everyone/View on them, and Everyone/Edit on all other issues in the Project.

Also, I only have access to the JIRA interface; no access to the JIRA database, or the server we are hosting our on-prem install.  I am also generally not allowed to install add-ons, even free ones because of security/privacy risks...

[Jimmy Van (GLiNTECH) · Accepted solution]

Hi Sienca,

Can you tell me a little more about the issue types? Do they all share the same workflow? Would it be possible to split the workflows?

Issue Security limits visibility, but you may be able to achieve what you want, without installing an add-on if you can split the worfklows.

[S]

They have a unique workflow and I know how to limit the Status changes to certain groups only.  But I need to split the issue into View only for one group and View + Edit (ie. changing the Description) permissions for another group.

[Jimmy Van (GLiNTECH)]

Ok if they have a unique workflow, have a look at workflow properties.

They're documented here: https://confluence.atlassian.com/adminjiraserver073/workflow-properties-861253674.html

Specifically, I'm thinking look at jira.permission.edit.group=specialgroup1

As it's attached to the workflow, and that workflow is matched to the issue type you want to lock down. Let me know how you go

[S]

Oh!  That seems to have worked.  Thank you very much!