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.

    • 3
    • 81
    • Hide
      Atlassian Update – 4 April 2019

      Hi everyone,

      In the latest update, we shared that to solve the problem of renaming groups in Jira we would have to make fundamental, breaking changes, which would probably need a new platform release. We understand that this issue is causing extra workload and pain, that’s why we want to provide some guidance and support. 

      We prepared a knowledge base article that explains how to manually rename groups through the database, similarly to Confluence. We learned from you that an article like that would indeed be helpful. Please note that this procedure is not part of the Jira’s intended functionality, and the information is provided as-is. This is only a way of providing a solution as soon as possible. For customized Jira instances using multiple apps, this might not be sufficient, though. The scripts will update the group names in the Jira platform, which is shared between Jira Core, Jira Software, and Jira Service Desk (the latter two are built on top of the platform). It might happen that group names are also stored in places specific to Jira Software, Jira Service Desk or Portfolio for Jira, and these won’t be updated.

      We still plan to solve the underlying problem and prioritize this suggestion for future consideration. We will post an update when new information is available.

      Katarzyna Derenda
      Product Manager, Jira Server

      Show
      Atlassian Update – 4 April 2019 Hi everyone, In the latest update, we shared that to solve the problem of renaming groups in Jira we would have to make fundamental, breaking changes, which would probably need a new platform release. We understand that this issue is causing extra workload and pain, that’s why we want to provide some guidance and support.  We prepared a  knowledge base article  that explains how to manually rename groups through the database, similarly to Confluence. We learned from you that an article like that would indeed be helpful. Please note that this procedure is not part of the Jira’s intended functionality, and the information is provided as-is. This is only a way of providing a solution as soon as possible. For customized Jira instances using multiple apps, this might not be sufficient, though. The scripts will update the group names in the Jira platform, which is shared between Jira Core, Jira Software, and Jira Service Desk (the latter two are built on top of the platform). It might happen that group names are also stored in places specific to Jira Software, Jira Service Desk or Portfolio for Jira, and these won’t be updated. We still plan to solve the underlying problem and prioritize this suggestion for future consideration. We will post an update when new information is available. Katarzyna Derenda Product Manager, Jira Server
    • 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.

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

      Original request description:

      As a JIRA administrator I am responsible for managing a large installation with multiple users and groups. Given the dynamic nature of my environment it is very difficult for me to create the correct user group name which can be used for many projects later on. I need to be able to rename the user groups, to reflect the changes my organisation undergoes.

        1. celebrating-12-plus-of-being-ignored.png
          celebrating-12-plus-of-being-ignored.png
          99 kB
        2. Crowd Database Schema.png
          Crowd Database Schema.png
          19 kB
        3. Group_AddForProjectsAndRoles.groovy
          3 kB
        4. GroupHelper.groovy
          10 kB
        5. JIRA group name changed.png
          JIRA group name changed.png
          147 kB
        6. JIRA-rename-groups.xlsx
          9 kB
        7. Lombiq.jpg
          Lombiq.jpg
          724 kB
        8. screenshot-1.png
          screenshot-1.png
          16 kB
        9. screenshot-2.png
          screenshot-2.png
          3 kB

            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.

              • 3
              • 81
              • Hide
                Atlassian Update – 4 April 2019

                Hi everyone,

                In the latest update, we shared that to solve the problem of renaming groups in Jira we would have to make fundamental, breaking changes, which would probably need a new platform release. We understand that this issue is causing extra workload and pain, that’s why we want to provide some guidance and support. 

                We prepared a knowledge base article that explains how to manually rename groups through the database, similarly to Confluence. We learned from you that an article like that would indeed be helpful. Please note that this procedure is not part of the Jira’s intended functionality, and the information is provided as-is. This is only a way of providing a solution as soon as possible. For customized Jira instances using multiple apps, this might not be sufficient, though. The scripts will update the group names in the Jira platform, which is shared between Jira Core, Jira Software, and Jira Service Desk (the latter two are built on top of the platform). It might happen that group names are also stored in places specific to Jira Software, Jira Service Desk or Portfolio for Jira, and these won’t be updated.

                We still plan to solve the underlying problem and prioritize this suggestion for future consideration. We will post an update when new information is available.

                Katarzyna Derenda
                Product Manager, Jira Server

                Show
                Atlassian Update – 4 April 2019 Hi everyone, In the latest update, we shared that to solve the problem of renaming groups in Jira we would have to make fundamental, breaking changes, which would probably need a new platform release. We understand that this issue is causing extra workload and pain, that’s why we want to provide some guidance and support.  We prepared a  knowledge base article  that explains how to manually rename groups through the database, similarly to Confluence. We learned from you that an article like that would indeed be helpful. Please note that this procedure is not part of the Jira’s intended functionality, and the information is provided as-is. This is only a way of providing a solution as soon as possible. For customized Jira instances using multiple apps, this might not be sufficient, though. The scripts will update the group names in the Jira platform, which is shared between Jira Core, Jira Software, and Jira Service Desk (the latter two are built on top of the platform). It might happen that group names are also stored in places specific to Jira Software, Jira Service Desk or Portfolio for Jira, and these won’t be updated. We still plan to solve the underlying problem and prioritize this suggestion for future consideration. We will post an update when new information is available. Katarzyna Derenda Product Manager, Jira Server
              • 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.

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

                Original request description:

                As a JIRA administrator I am responsible for managing a large installation with multiple users and groups. Given the dynamic nature of my environment it is very difficult for me to create the correct user group name which can be used for many projects later on. I need to be able to rename the user groups, to reflect the changes my organisation undergoes.

                  1. celebrating-12-plus-of-being-ignored.png
                    celebrating-12-plus-of-being-ignored.png
                    99 kB
                  2. Crowd Database Schema.png
                    Crowd Database Schema.png
                    19 kB
                  3. Group_AddForProjectsAndRoles.groovy
                    3 kB
                  4. GroupHelper.groovy
                    10 kB
                  5. JIRA group name changed.png
                    JIRA group name changed.png
                    147 kB
                  6. JIRA-rename-groups.xlsx
                    9 kB
                  7. Lombiq.jpg
                    Lombiq.jpg
                    724 kB
                  8. screenshot-1.png
                    screenshot-1.png
                    16 kB
                  9. screenshot-2.png
                    screenshot-2.png
                    3 kB

                        Unassigned Unassigned
                        ec0850b43996 BR DevOps
                        Votes:
                        23 Vote for this issue
                        Watchers:
                        13 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            ec0850b43996 BR DevOps
                            Votes:
                            23 Vote for this issue
                            Watchers:
                            13 Start watching this issue

                              Created:
                              Updated: