Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-81740

Ability to limit who is able to create a new team and who is able to delete any team

    • 1,452
    • 90
    • 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.

      In regard to permissions, it would be useful to have the ability to limit who is able to create a new team / change name of the team and who is able to delete any team.

      With Upcoming change in ARJ, about combining the Atlassian Team with ARJ Shared team, this feature has become more relevant for Enterprise Customers. As they follow strict Team naming conventions, it will be difficult for them to control the team creation.

            [JRACLOUD-81740] Ability to limit who is able to create a new team and who is able to delete any team

            I just had a user delete a Team in the wrong place (the permanent delete in the module as opposed to the Plan delete), it's was on the data center version but I know that Atlassian is not making updates to Data Center. With no audit log we are scrambling to see if our reporting database backed up this data, our staging is old by 3 weeks. If you leave this permission open there has to be a way to track back... I didn't see the ability to resurrect an ID, is it possible that "delete" could be more like the archive function in Components? That way a user might remove it from dropdown options but the data is still available? I have to say this definitely a weird gap, but when someone steps into it, boy is it hard to close.

            Crystelle S added a comment - I just had a user delete a Team in the wrong place (the permanent delete in the module as opposed to the Plan delete), it's was on the data center version but I know that Atlassian is not making updates to Data Center. With no audit log we are scrambling to see if our reporting database backed up this data, our staging is old by 3 weeks. If you leave this permission open there has to be a way to track back... I didn't see the ability to resurrect an ID, is it possible that "delete" could be more like the archive function in Components? That way a user might remove it from dropdown options but the data is still available? I have to say this definitely a weird gap, but when someone steps into it, boy is it hard to close.

            If we could restrict the Team field to show only managed Teams, that would make the new feature more useful.

            We want the kind of Admin permissions for Teams that we have for projects. I continue to be baffled by what research led to these design decisions

            Jennifer D Smith added a comment - If we could restrict the Team field to show only managed Teams, that would make the new feature more useful. We want the kind of Admin permissions for Teams that we have for projects. I continue to be baffled by what research led to these design decisions

            Hanna Torany added a comment - - edited

            I already know about the Managed Teams. This is very good feature but the user will still be able to create invite-only or open team and this will lead to lack of control over team management.

             

            Atlassian should give the customer a way to restrict this access.

            Hanna Torany added a comment - - edited I already know about the Managed Teams. This is very good feature but the user will still be able to create invite-only or open team and this will lead to lack of control over team management.   Atlassian should give the customer a way to restrict this access.

            Ralf Scheller added a comment - Yes, take a look on the New Feature "Managed Teams" - https://community.atlassian.com/forums/Jira-Service-Management-articles/Managed-Teams-are-now-available-for-Premium-and-Enterprise/ba-p/2961740?utm_source=atlcomm&utm_medium=email&utm_campaign=&utm_content=post  

            4b7910ae10b4  Is there any news here?

            Hanna Torany added a comment - 4b7910ae10b4   Is there any news here?

             
             

            Function Description Team Assignment Group “Asset field” Assignment Group Picker
            Show Assignable group Show only the groups that used to assign issue to a team.
            Sync with Active Directory Sync Name and Members from AD Group.
            Bulk change Give the user possibility to bulk change the assigned team in several tickets at the same time .
            Dynamic Board / Queue Show the tickets that assigned to the team where the current user is member of.
            Available in Forms Add a field in Forms where the requestor can select the team.
            Use to set Permissions Give a team a specific permission

             
             
            Atlassian is working on development of “Team” field. When we get all the functions that needed, we can stop the sync between the fields and remove “Assignment Group” field and “Assignment Group Picker” field.

            Here is the feature requests:

            • JRACLOUD-81740 Ability to limit who is able to create a new team and who is able to delete any team
            • JRACLOUD-81399 Restrict a Team to see only tickets associated with them

            Hanna Torany added a comment -     Function Description Team Assignment Group “Asset field” Assignment Group Picker Show Assignable group Show only the groups that used to assign issue to a team. Sync with Active Directory Sync Name and Members from AD Group. Bulk change Give the user possibility to bulk change the assigned team in several tickets at the same time . Dynamic Board / Queue Show the tickets that assigned to the team where the current user is member of. Available in Forms Add a field in Forms where the requestor can select the team. Use to set Permissions Give a team a specific permission     Atlassian is working on development of “ Team ” field. When we get all the functions that needed, we can stop the sync between the fields and remove “Assignment Group” field and “Assignment Group Picker” field. Here is the feature requests: JRACLOUD-81740 Ability to limit who is able to create a new team and who is able to delete any team JRACLOUD-81400 Add support for membersOf JQL function for Teams JRACLOUD-84663 JQL Search for Team does not Recognize Team Names JRACLOUD-81399 Restrict a Team to see only tickets associated with them

            Brad Wood added a comment -

            Has there been any forward progress on this feature request?

            Brad Wood added a comment - Has there been any forward progress on this feature request?

            Jonathan Rosenfeld added a comment - - edited

            Due to no option to prevent team members from deleting teams we may need to back out of our migration from Pagerduty to Jira Incident Management. 

             

            No ability to prevent this is very problematic.

             

            Edit: After additional testing we see an email is sent to team members when a team is deleted and then there are 30 days after deletion to recover a team. This eases our concerns for migration

            Jonathan Rosenfeld added a comment - - edited Due to no option to prevent team members from deleting teams we may need to back out of our migration from Pagerduty to Jira Incident Management.    No ability to prevent this is very problematic.   Edit: After additional testing we see an email is sent to team members when a team is deleted and then there are 30 days after deletion to recover a team. This eases our concerns for migration

            +1

            Any plans on adding groups to the team, manually or automatically through IDPs?

            Vedant Kulkarni_Trundl added a comment - +1 Any plans on adding groups to the team, manually or automatically through IDPs?

            Do you have any update here? This feature is important for us. We have a lot of problem now.

            Hanna Torany added a comment - Do you have any update here? This feature is important for us. We have a lot of problem now.

              4b7910ae10b4 April Chi
              5de0cfe260fe William (Inactive)
              Votes:
              302 Vote for this issue
              Watchers:
              174 Start watching this issue

                Created:
                Updated: