-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Issue Summary
Private teams (Scenarios) are not comparable with shared team because:
- Private teams (Scenarios) scope visibility only within the 1 plan - not sharable with other plans
- Private teams (Scenarios) are not available as custom field on issue view/create screens
On the other hand shared teams are not having above two limitations but having below data privacy issues:
- JIRA DC is build fTextor enterprise teams. This means multiple teams can parallel/securely work on single JIRA DC instance. NO NEW FEATURE REQUESTED, THIS IS MVP FOR ANY ENTERPRISE SOLUTION - EXPECTED FROM DAY-0 OF PRODUCT LAUCH
- Data privacy / NFR is P1 requirement for any enterprise teams. NO NEW FEATURE REQUESTED, THIS IS MVP FOR ANY ENTERPRISE SOLUTION - EXPECTED FROM DAY-0 OF PRODUCT LAUCH
- This is blocker issue for enterprise JIRA DC instance and we are running one of them. This is a blocker issue for Advance roadmap adoption hence need urgent fix
If Atlassian build Advance Roadmap team feature for small team & small organisation then
- Update public facing Advance roadmap product page and clearly mention that this product is not for large enterprise - only suitable for small teams, small organisations
There is a feature request for the changes below:
This is reproducible on Data Center: (yes)
Steps to Reproduce
Scenario 1
- All users can see all Team members info via Manage Shared Teams page after granted Shared Team Permission
- We remove the users from the Browser Users global permission but still the problem can view all users in the Team tab.
Scenario 2
- Configure shared team management only jira-administrators group.
- Remove jira-software-users group from the Browser Users global permission.
- Remove jira-software-users group from the Browser Projects permission to browse the issues.
- Create a new plan > navigate to the teams.
- Add a new private team and add a member inside:
- Log in with a normal user that has jira-software-users group. Go to the plan and all users can see a private shared team user information:
Expected Results
If Atlassian build Advance Roadmap team feature for small team & small organisation then
- Update public facing Advance roadmap product page and clearly mention that this product is not for large enterprise - only suitable for small teams, small organisations
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-25290] Need a documentation update on the Advanced Roadmaps due to not supported Enterprise level design
| Support reference count | New: 1 |
| Labels | Original: API | New: API ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979779 ] |
| Component/s | Original: Documentation [ 36490 ] | |
| Component/s | New: (Advanced Roadmaps) API / Documentation [ 73718 ] | |
| Key | Original: JPOSERVER-4326 | New: JSWSERVER-25290 |
| Project | Original: Advanced Roadmaps [ 16510 ] | New: Jira Software Server and Data Center [ 12200 ] |
| Labels | New: API |
| Comment |
[ .
] |
| Affects Version/s | Original: 8.22.0 [ 98999 ] | |
| Workflow | Original: JAC Bug Workflow v3 [ 4275134 ] | New: JAC Suggestion Workflow 3 [ 4275136 ] |
| Issue Type | Original: Bug [ 1 ] | New: Suggestion [ 10000 ] |
| Priority | Original: Medium [ 3 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Interest [ 11772 ] |
| Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
| Summary | Original: Need a documentation update on the Advanced Roadmaps due to not supported more than 100+ clients | New: Need a documentation update on the Advanced Roadmaps due to not supported Enterprise level design |
| Description |
Original:
h3. Issue Summary
Private teams (Scenarios) are not comparable with shared team because: * Private teams (Scenarios) scope visibility only within the 1 plan - not sharable with other plans * Private teams (Scenarios) are not available as custom field on issue view/create screens On the other hand shared teams are not having above two limitations but having below data privacy issues: - JIRA DC is build fTextor enterprise teams. This means multiple teams can parallel/securely work on single JIRA DC instance. NO NEW FEATURE REQUESTED, THIS IS MVP FOR ANY ENTERPRISE SOLUTION - EXPECTED FROM DAY-0 OF PRODUCT LAUCH - Data privacy / NFR is P1 requirement for any enterprise teams. NO NEW FEATURE REQUESTED, THIS IS MVP FOR ANY ENTERPRISE SOLUTION - EXPECTED FROM DAY-0 OF PRODUCT LAUCH - This is blocker issue for enterprise JIRA DC instance and we are running one of them. This is a blocker issue for Advance roadmap adoption hence need urgent fix If Atlassian build Advance Roadmap team feature for small team & small organisation then - Update public facing Advance roadmap product page and clearly mention that this product is not for large enterprise - only suitable for small teams, small organisations There is a feature request for the changes below: * [As an Admin, I would like Shared Team Permissions to have project or plan level permission scaling|https://jira.atlassian.com/browse/JPOSERVER-4315] This is reproducible on Data Center: (yes) h3. Steps to Reproduce *Scenario 1* * All users can see all Team members info via Manage Shared Teams page after granted *Shared Team Permission* !team-members-visible-1.png|thumbnail! !team-members-visible-2.png|thumbnail! * We remove the users from the *Browser Users* global permission but still the problem can view all users in the Team tab. *Scenario 2* # Configure shared team management only *jira-administrators* group. !shared-team-permission-1.png|thumbnail! # Remove *jira-software-users* group from the *Browser Users* global permission. # Remove *jira-software-users* group from the *Browser Projects* permission to browse the issues. # Create a new plan > navigate to the teams. # Add a new private team and add a member inside: !private-team-1.png|thumbnail! # Log in with a normal user that has *jira-software-users* group. Go to the plan and all users can see a private shared team user information: !other-users-pov-1.png|thumbnail! h3. Expected Results * Make shared team feature identical to other shared configuration in JIRA. Make shared team visibility configurable at projects level or plans level by the JIRA administrator user (as like other shared JIRA configuration) * This solution will fix P1 – blocker data privacy issue in shared team feature h3. Actual Results Why this is not treated as new enhancement? Why this is a P1 product bug / design flow? Why this issue need urgent fix? * JIRA DC is build for enterprise teams. This means multiple teams can parallel/securely work on single JIRA DC instance. NO NEW FEATURE REQUESTED, THIS IS MVP FOR ANY ENTERPRISE SOLUTION - EXPECTED FROM DAY-0 OF PRODUCT LAUCH Data privacy / NFR is P1 requirement for any enterprise teams. NO NEW FEATURE REQUESTED, THIS IS MVP FOR ANY ENTERPRISE SOLUTION - EXPECTED FROM DAY-0 OF PRODUCT LAUCH * This is blocker issue for enterprise JIRA DC instance and we are running one of them. * This is a blocker issue for Advance roadmap adoption hence need urgent fix h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
Private teams (Scenarios) are not comparable with shared team because: * Private teams (Scenarios) scope visibility only within the 1 plan - not sharable with other plans * Private teams (Scenarios) are not available as custom field on issue view/create screens On the other hand shared teams are not having above two limitations but having below data privacy issues: - JIRA DC is build fTextor enterprise teams. This means multiple teams can parallel/securely work on single JIRA DC instance. NO NEW FEATURE REQUESTED, THIS IS MVP FOR ANY ENTERPRISE SOLUTION - EXPECTED FROM DAY-0 OF PRODUCT LAUCH - Data privacy / NFR is P1 requirement for any enterprise teams. NO NEW FEATURE REQUESTED, THIS IS MVP FOR ANY ENTERPRISE SOLUTION - EXPECTED FROM DAY-0 OF PRODUCT LAUCH - This is blocker issue for enterprise JIRA DC instance and we are running one of them. This is a blocker issue for Advance roadmap adoption hence need urgent fix If Atlassian build Advance Roadmap team feature for small team & small organisation then - Update public facing Advance roadmap product page and clearly mention that this product is not for large enterprise - only suitable for small teams, small organisations There is a feature request for the changes below: * [As an Admin, I would like Shared Team Permissions to have project or plan level permission scaling|https://jira.atlassian.com/browse/JPOSERVER-4315] This is reproducible on Data Center: (yes) h3. Steps to Reproduce *Scenario 1* * All users can see all Team members info via Manage Shared Teams page after granted *Shared Team Permission* !team-members-visible-1.png|thumbnail! !team-members-visible-2.png|thumbnail! * We remove the users from the *Browser Users* global permission but still the problem can view all users in the Team tab. *Scenario 2* # Configure shared team management only *jira-administrators* group. !shared-team-permission-1.png|thumbnail! # Remove *jira-software-users* group from the *Browser Users* global permission. # Remove *jira-software-users* group from the *Browser Projects* permission to browse the issues. # Create a new plan > navigate to the teams. # Add a new private team and add a member inside: !private-team-1.png|thumbnail! # Log in with a normal user that has *jira-software-users* group. Go to the plan and all users can see a private shared team user information: !other-users-pov-1.png|thumbnail! h3. Expected Results If Atlassian build Advance Roadmap team feature for small team & small organisation then - Update public facing Advance roadmap product page and clearly mention that this product is not for large enterprise - only suitable for small teams, small organisations h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |