-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Definition
For organizations with multiple client projects, it is crucial to have this Team field restricted as they don't want other users to see this information.
Ideally, we have to use private team but when the team is private it doesn't allow to fetch team details in Jira issue detail pages hence we use shared team concept.
Suggestion
Ability to restrict Team field visibility in project level.
- links to
Form Name |
---|
[JSWSERVER-25246] Restrict Portfolio Shared Team per project
Labels | Original: Plan-Team | New: Plan-Team ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979736 ] |
UIS | Original: 0 | New: 1 |
Component/s | Original: Usability [ 47601 ] | |
Component/s | New: (Advanced Roadmaps) Plan - Teams [ 63500 ] | |
Key | Original: JPOSERVER-2754 | New: JSWSERVER-25246 |
Project | Original: Advanced Roadmaps [ 16510 ] | New: Jira Software Server and Data Center [ 12200 ] |
Labels | New: Plan-Team |
UIS | Original: 7 | New: 0 |
UIS | New: 7 |
Hello!
Wanting to re-raise this issue as something that is very important to my company. I work for a very large company and the teams dropdown exposes too much information, and potentially classified information.
Please let me know if you would like more information!
Best,
Younghu