-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.20.0, 8.22.0
-
8.2
-
2
-
Severity 2 - Major
-
1
-
Expected Behavior
Only users with "Shared Team Management" are able to edit a shared team, or share a presently private team.
Actual Behavior
Any user with access to a plan in which any team is added can modify that team - regardless of it being shared or private - or share a private team.
Steps to Reproduce
- Create any team and add it to a plan accessible by any user;
- Access the plan as a user without "Shared Team Management" permission;
Workaround
There is no known workaround at this time.
- relates to
-
JSWSERVER-25253 Add possibility to unshare a team.
- Under Consideration
-
JPOS-1673 You do not have permission to view this issue
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-24779] BUG: Manage shared team is allowed even if "Shared Team Management" permission is not granted
Hello @qfeyaerts
is there any advice how users should proceed, now after you closed this issue?
On the one hand we are even happy that it won't be changed, as this bug was kind of the only way to use Teams in Jira (not Portfolio) without giving thousands of users the shared team mgmt persmission (which cannot be done as that admin interface is rather rudimentary, everybody could change delete teams of others without notice)
BR
Exactly the same Issue here v 2.10.0
Portfolio Users also cannot be reduced due to this missing function: https://jira.atlassian.com/browse/JPOSERVER-1681
It is also not possible to unshare the teams, I would have to delete them 
: (https://jira.atlassian.com/browse/JPOSERVER-1544 ).
REST endpoint responsible for sharing portfolio team is not limited to Jira administrators or users with 'Shared Team Management' permission.
Every Jira user is able to send POST request to: /rest/teams/1.0/teams/{team_id}/setShared and share any team !
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC