Uploaded image for project: 'Identity'
  1. Identity
  2. ID-8904

Ability to retain the team name when connected to a managed group.

XMLWordPrintable

    • 4

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

      Currently, We change the name of the team to the managed group when connecting an Existing team to the group. It would be preferred to use the existing team name when connecting it to a managed group. 

      Adding one more use case to this feature request:

      Please introduce a way to edit the Team name after synchronization with Jira group? 

      After synchronization, it is not possible to edit the team name anymore, which makes it impossible to have a friendly name for the team because Jira groups are often synchronized with Entra ID or Active Directory and have peculiar names.

            [ID-8904] Ability to retain the team name when connected to a managed group.

            SET Analytics Bot made changes -
            Support reference count Original: 3 New: 4

            Daniel.Pancorbo added a comment - - edited

            Same request,

            for large solutions using teams (especially solution that makes usage of plans) it is convenient to have a friendly alias.

            Can be also important to have a couple of extra enhancements:

            • Many groups to one Jira team ( so I can sum the users from many Jira groups to one single Jira Team)
            • One group to many Jira team ( so I can synchronize the same group of users in multiple virtual teams)

            Without team renaming feature and these two extra features, the "Team" in Jira is going to be not useful for users and companies

            Daniel.Pancorbo added a comment - - edited Same request, for large solutions using teams (especially solution that makes usage of plans) it is convenient to have a friendly alias. Can be also important to have a couple of extra enhancements: Many groups to one Jira team ( so I can sum the users from many Jira groups to one single Jira Team) One group to many Jira team ( so I can synchronize the same group of users in multiple virtual teams) Without team renaming feature and these two extra features, the "Team" in Jira is going to be not useful for users and companies
            Darya Kunitskaya made changes -
            Description Original: Currently, We change the name of the team to the managed group when connecting an Existing team to the group. It would be preferred to use the existing team name when connecting it to a managed group.  New: Currently, We change the name of the team to the managed group when connecting an Existing team to the group. It would be preferred to use the existing team name when connecting it to a managed group. 
            h4. Adding one more use case to this feature request:

            Please introduce a way to edit the Team name after synchronization with Jira group? 

            After synchronization, it is not possible to edit the team name anymore, which makes it impossible to have a friendly name for the team because Jira groups are often synchronized with Entra ID or Active Directory and have peculiar names.

            Knut Arne Ristebråten added a comment -

            I agree to this.

            Using the group name can cause inlogical team names.
            When using a sentralized user management system the naming of the groups are important. Even default Atlassian groups are in a name structure (e.g. jira-product-discovery-users-sitename).

            For example if we are to have a team called "Most awesome team ever" the group name in our IDP might have a struture of atlassian-team-most-awesome-team-ever.
            Having the team named like this is no good. We cannot have groups with no structure, spaces etc..

            Being able to sert a custom team name, and connect a group with a different group name is required for us to actually use this feature.

            Knut Arne Ristebråten added a comment - I agree to this. Using the group name can cause inlogical team names. When using a sentralized user management system the naming of the groups are important. Even default Atlassian groups are in a name structure (e.g. jira-product-discovery-users-sitename). For example if we are to have a team called "Most awesome team ever" the group name in our IDP might have a struture of atlassian-team-most-awesome-team-ever. Having the team named like this is no good. We cannot have groups with no structure, spaces etc.. Being able to sert a custom team name, and connect a group with a different group name is required for us to actually use this feature.
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            Abhishek made changes -
            Description Original: Currently, it is not possible to rename the managed teams. Such teams take the name of the provisioned group. Connecting Teams to Groups and keeping the Group name is problematic as end users don’t understand the team name.

             

            Advice: Provide the ability for the organisation admins to rename the managed teams.             		New: Currently, We change the name of the team to the managed group when connecting an Existing team to the group. It would be preferred to use the existing team name when connecting it to a managed group. 
            Abhishek made changes -
            Summary Original: Ability to rename managed teams New: Ability to retain the team name when connected to a managed group.
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            SET Analytics Bot made changes -
            Support reference count New: 1
            Abhishek created issue -

              Unassigned Unassigned
              b23de49ea095 Abhishek
              Votes:
              12 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: