We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 1
    • 13
    • 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.

      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

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 1
              • 13
              • 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.

                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

                        Unassigned Unassigned
                        soslopov Sergey
                        Votes:
                        16 Vote for this issue
                        Watchers:
                        19 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            soslopov Sergey
                            Votes:
                            16 Vote for this issue
                            Watchers:
                            19 Start watching this issue

                              Created:
                              Updated: