Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-5865

Allow permission schemes to be configured per issue type

    XMLWordPrintable

    Details

    • Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.
    • Current Status:
      Hide
      Atlassian Update – 1 October 2018

      Hi everyone,

      Thank you for sharing your comments on permission schemes per issue type. This suggestion has been resolved as Won’t Fix in 2011, but recently, while updating the workflow for all suggestions on jira.atlassian.com we have changed the status from Closed to Resolved. This technical change triggered a few questions from you, so we’ve decided to post an update for clarity.

      We have reviewed this suggestion again and how it would fit alongside our strategy and other customer priorities. We will not be re-opening the suggestion because we are not planning to invest in adding permissions per issue type in Jira. While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity. We stand by the decision posted by Roy Krishna in 2011 in this comment.

      Meanwhile, in some of the contexts this knowledge base article can be useful How to set the Security Level of an issue based on group membership.

      Kind regards
      Katarzyna Derenda
      Product manager, Jira Server

       

      Show
      Atlassian Update – 1 October 2018 Hi everyone, Thank you for sharing your comments on permission schemes per issue type. This suggestion has been resolved as Won’t Fix in 2011, but recently, while updating the workflow for all suggestions on jira.atlassian.com we have changed the status from Closed to Resolved. This technical change triggered a few questions from you, so we’ve decided to post an update for clarity. We have reviewed this suggestion again and how it would fit alongside our strategy and other customer priorities. We will not be re-opening the suggestion because we are not planning to invest in adding permissions per issue type in Jira. While we absolutely understand the logic behind this request, we strongly believe that we should focus on making Jira simpler and easier to use rather then introduce additional complexity. We stand by the decision posted by Roy Krishna in 2011 in this comment. Meanwhile, in some of the contexts this knowledge base article can be useful  How to set the Security Level of an issue based on group membership . Kind regards Katarzyna Derenda Product manager, Jira Server  

      Description

      Now, when a group has the permission to create an issue, it could create EVERY types of issues available. It's a complement to project specific issues types. (http://jira.atlassian.com/browse/JRA-1602)

      For example, If we have external client (like me right now ) I would be interrested to limit his issue creation right to only bugs, features, external client requests (custom type).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ajskdlf ajskdlf
              • Votes:
                327 Vote for this issue
                Watchers:
                390 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: