Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-62162

Regarding restricting view based on issue type

XMLWordPrintable

    • 0
    • 19

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Problem:

      There is a need to be able to restrict viewing of issue types in a project based on groups.

      Example : Users in Team1 should be able to view and create all issue types (epic, story, task, bug) ( this is the default behaviour and all good ), while users in team2 should be able to just view issue type bug alone in the particular project.

      Suggestion:

      Add a post function or permission on the project that it will be possible to restrict the view of issues by issue type.

            [JRACLOUD-62162] Regarding restricting view based on issue type

            Anusha Rutnam added a comment -
            Atlassian Update - February 2024

            As I did not receive any responses to this comment I am closing this ticket.

            If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - February 2024 As I did not receive any responses to this comment I am closing this ticket. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment -

            It's possible to restrict who can view an issue based on issue type as documented in this article: Restrict Agents access based on Issue Type

            Though it refers specifically to Agents, the restriction can be done for any group of users. Does this satisfy the requirements of the watchers of this ticket? Thank you!

             

            Anusha Rutnam added a comment - It's possible to restrict who can view an issue based on issue type as documented in this article: Restrict Agents access based on Issue Type Though it refers specifically to Agents, the restriction can be done for any group of users. Does this satisfy the requirements of the watchers of this ticket? Thank you!  

            Max added a comment -

            It would be useful to restrict view/edit based on issue type for cross-functional teams. For example, we have an ITSD project and want to use the Change Management feature to centralise change management across the business. However, the other teams do not need view/edit access to incident/service requests/etc.

            Max added a comment - It would be useful to restrict view/edit based on issue type for cross-functional teams. For example, we have an ITSD project and want to use the Change Management feature to centralise change management across the business. However, the other teams do not need view/edit access to incident/service requests/etc.

            Peter Saro added a comment -

            We would like to restrict visibility of selected issue types for users from different locations on customer portal.

            Peter Saro added a comment - We would like to restrict visibility of selected issue types for users from different locations on customer portal.

            RemiC added a comment -

            I would like to be able to "archive" or hide issue-types. We have a case where we added new issue types depending on the type of work (for time logging purposes) and don't want devs to use the old issue type anymore without loosing history or having to change that old one to a different issue type.

            RemiC added a comment - I would like to be able to "archive" or hide issue-types. We have a case where we added new issue types depending on the type of work (for time logging purposes) and don't want devs to use the old issue type anymore without loosing history or having to change that old one to a different issue type.

              Unassigned Unassigned
              pmiguel Paulo Miguel (Inactive)
              Votes:
              12 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: