• 1
    • 4
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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.

            [JSWSERVER-25246] Restrict Portfolio Shared Team per project

            SET Analytics Bot made changes -
            Support reference count New: 4
            Marc Dacanay made changes -
            Labels Original: Plan-Team New: Plan-Team ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 979736 ]
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            Aakrity Tibrewal made changes -
            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 ]
            Stasiu made changes -
            Labels New: Plan-Team
            SET Analytics Bot made changes -
            UIS Original: 7 New: 0
            SET Analytics Bot made changes -
            UIS New: 7
            Anna Cardino (Inactive) created issue -

              Unassigned Unassigned
              acardino Anna Cardino (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: