• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Board configuration
    • None
    • 1
    • 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.

      This feature suggestion is to implement a new permission for "Change Issue type" in JIRA which will allow JIRA administrators to prevent users from changing issue types when moving issues between projects, or when performing bulk updates etc.

      Use case:

      Changing issue types can lead to various consequences and impact JIRA add-ons which are dependant on this field.

      In Jira Portfolio pans for example, when changes are done to items that are on JIRA Portfolio plans – these items just disappear from the plans

      Having an ability to restrict users from changing issue type would prevent this situation and would allow more flexibility to configure JIRA permissions

            [JSWSERVER-16459] Change Issue type permission

            Atlassian Update – 27 September 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 27 September 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

            Sergey added a comment - - edited

            Sergey added a comment - - edited another use case https://jira.atlassian.com/browse/JPOSERVER-1909

            Sergey added a comment - - edited

            Sergey added a comment - - edited another user case https://jira.atlassian.com/browse/JRASERVER-16521

            Sergey added a comment -

            Sergey added a comment - https://getsupport.atlassian.com/browse/JPO-2793

              Unassigned Unassigned
              soslopov Sergey
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: