-
Suggestion
-
Resolution: Unresolved
-
1,452
-
90
-
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.
- relates to
-
JRACLOUD-75734 Ability to prevent users from using the "start a team" option in Jira
- Under Consideration
- is resolved by
-
ACE-4325 You do not have permission to view this issue
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
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.