Access control : story issue type or new issue type

[Sarthak Sachdeva]

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?

[Trudy P Claspill]

This post is a duplicate of your earlier post to which an answer has already been provided.

https://community.atlassian.com/t5/Jira-questions/What-are-the-capabilities-of-access-control-on-the-issue-type/qaq-p/2726602

Coincidentally I have also already addressed those same questions in a post from a different community member.

https://community.atlassian.com/t5/Jira-questions/Access-control-in-story-issue-type-or-new-issue-type/qaq-p/2722573