What are the capabilities of access control on the issue type

Sarthak Sachdeva June 13, 2024

Can we access to the story issue type be limited to create and view for a specific group of users?

Need Documentation for clarification

1 answer

0 votes
J. Caldwell
Contributor
June 13, 2024

So, you would be looking project by project. 

For the create action, you could add a condition to the "create" action of the workflow for a specific project (company managed project) for the Story issue type that the user be either in a specific group or role within the project. If it is broader than just story, permissions and the "Create issue" permission would be a way to control things. 

For viewing issues, there are a couple of ways you could accomplish things. Issue level security would be a way where you create scheme and have a level for "Story" -> You then define the groups/roles/people that have access to that level. You would need to have automation run to auto-set the security level (or via workflow) for Stories to that one level.

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Sarthak Sachdeva June 13, 2024

A squad that supports planned enhancement work as well as production support requests needs a way to manage the intake of the prod supp requests. Stakeholders who are not part of the squad will submit production support requests in Jira as Stories or some other issue type. The squad wants to limit the stakeholder’s access to create and view access only.

We need to understand the capabilities of access control on the Story issue type or on a new issue type that may be used for this purpose. The preference is to restrict access to Stories so all of the squad’s work is managed on the same issue type.

 

Question : 1)

Answers to the following questions are needed.

1) Can access to the Story issue type be limited to Create and View for a specific group of users?
(Please include any documentation regarding issue access control)
2)Can access to a new unique issue type be limited to Create and View for a specific group of users?
If so, are one of the following options possible?
-Can this issue type be converted to a Story by a member of the squad with full edit access?
-Can this issue be updated to indicate a Story as its Parent?

Suggest an answer

Log in or Sign up to answer