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.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-36637

When deleting a group, I should be prompted to change the sharing information for dashboards and filters

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

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

      Our users have been assigned to new groups on the basis of a corporate restructuring. The group names have been used for sharing filters, dashboards and comments.

      If I delete the old groups, then JIRA asks for a new group name so that shared comments can be changed to the new group. That's great!

      Unfortunately, this does not apply shared filters and dashboards. The filters and dashboards are no longer shared for other users.

      Therefore, we have stopped deleting the groups. However, new employees are not added to the old groups. This will end in chaos, because we do not know exactly whether groups are still needed or not. The system becomes increasingly cluttered.

      It would be nice if the shares of filters and dashboards could be changed to a different group, if groups are deleted. So just as it is already done for comments.

            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.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-36637

            When deleting a group, I should be prompted to change the sharing information for dashboards and filters

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

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

                Our users have been assigned to new groups on the basis of a corporate restructuring. The group names have been used for sharing filters, dashboards and comments.

                If I delete the old groups, then JIRA asks for a new group name so that shared comments can be changed to the new group. That's great!

                Unfortunately, this does not apply shared filters and dashboards. The filters and dashboards are no longer shared for other users.

                Therefore, we have stopped deleting the groups. However, new employees are not added to the old groups. This will end in chaos, because we do not know exactly whether groups are still needed or not. The system becomes increasingly cluttered.

                It would be nice if the shares of filters and dashboards could be changed to a different group, if groups are deleted. So just as it is already done for comments.

                        Unassigned Unassigned
                        be8c93b73c47 Max Doppler
                        Votes:
                        2 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            be8c93b73c47 Max Doppler
                            Votes:
                            2 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: