Access control in story issue type or new issue type
Asked by Roy:

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)

1. 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?
   1. Can this issue type be converted to a Story by a member of the squad with full edit access?
   2. Can this issue be updated to indicate a Story as its Parent?


Answers:
author: Trudy Claspill
body: Hello [@Roy](/t5/user/viewprofilepage/user-id/4665291)

With what type of project are you working? You can find that information in the Type column on the View All Projects page under the Projects menu.

1a. With native Jira functionality it is not possible to prevent a user from selecting any of the available issue types (in the project) when creating a new issue. You can add a Validation/Rule that would prevent saving the issue if the user should not be allowed to create that type of issue.

1b. It is possible to restrict a persons ability to access an issue after the issue has been created. The exact method to do this depends on the type of project with which you are working.

1c. However, permissions to edit issues applies to all issues within the project that the user can access. So, if the user is able to access the issue, and they have the Edit Issues permission in the project, then they will be able to Edit the issue. You could restrict the users from being able to edit **any** issue in the project, but you can't restrict them to being able to edit some issue types and only view others.

2a. See my answer on 1a.

2b. A member of the team with appropriate permissions would be able to change the issue type to any other valid issue type. Note that when that is done, the original reporter may lose access to the issue because the issue type is changed.

2c. A Story issue type can have only Subtask issue types as children. If the issue of concern is initially created as an issue type at the same level as Story, then it would have to be converted to a Subtask in order to make it a child of another Story. Note that when that is done, the original reporter may lose access to the issue because the issue type is changed.

comments: author: Roy
body: My question is ,its possible Can we access to the Story issue type be limited to Create and View for a specific group of users?


author: Trudy Claspill
body: My response contains the answer to those questions.

Let me try to simplify my answer.

*With native Jira functionality,*no, you can't limit the Create action to a subset of issue types in a project for a group of users.

* You can add a Validator to the Create transition in the Workflow for the various issue types to prevent the user group from being able to **save** an issue of a specified issue type, but they won't see that until after the enter the data in the Create Issue dialog and attempt to save the issue.

Yes, you can limit the user group's ability to View issues based on issue type. This would involve the configuration of Issue Security. The method for implementing issue security depends on the type of project with which you are working.


author: Roy
body: Hi Trudy

Can you please update what are point I have mention its possible in (Yes or NO ) so i will clear


author: Trudy Claspill
body: Hello [@Roy](/t5/user/viewprofilepage/user-id/4665291)

Perhaps we have a language barrier. Is English your native language?

You are asking more than one question in each of your points.

1. Can access to a new unique issue type be limited to **Create** ~~and View~~ for a specific group of users?

Answer: It depends.

If you only have native Jira functionality, then the answer is **NO**. A user with the Create Issue permission in the project can select any issue type available in the project after click the Create button.

1. Can access to a new unique issue type be limited to ~~Create and~~ **View** for a specific group of users?

Answer: **YES**

2.1 Can this issue type be converted to a Story by a member of the squad with full edit access?

Answer: It depends

A user must have access to view the issue, and Edit issues, and Move issues in order to change the issue type for an issue.

2.2 Can this issue be updated to indicate a Story as its Parent?

Answer: **NO**


author: Roy
body: Thank Trudy for the information


author: Roy
body: Actually English is not my native language Trudy thanks for understanding.


author: Trudy Claspill
body: You're welcome.


author: Roy
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)

Can a project be set to that ALL the Jira users have access without having to the list all names in the project Setup?


Tags: cloud

jira-cloud