• 6
    • 20
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem

      Comment restriction was added to the new issue view, but it didn't include team-managed (formerly next-gen) projects, so currently, the comments are visible to anyone that has access to the project.

      Suggestion

      Add the comment restriction feature to team-managed (formerly next-gen) projects.

      Workaround

      The comment visibility can be set from the search results in the Issue Navigator (List view).

      1. Search for issues in the Issue Navigator
      2. Switch to List view
      3. In the list view, you can choose to add comment and perform other actions on individual issues without opening them
      4. Add comment and notice you'll have an option to restrict the visibility

      Note: Once the comment visibility is set it can't be edited from the issue view.

      Comment visibility can be removed using the Update comment REST API call:

      curl --request PUT \
        --url 'https://your-domain.atlassian.net/rest/api/2/issue/{issueIdOrKey}/comment/{id}' \
        --user 'email@example.com:<api_token>' \
        --header 'Accept: application/json' \
        --header 'Content-Type: application/json' \
        --data '{
        "body": "Remove comment visibility restriction.",
        "visibility": null
      }'
      

        1. classic.png
          classic.png
          65 kB
        2. next-gen.png
          next-gen.png
          46 kB

          Form Name

            [JRACLOUD-83171] Comment restriction for team-managed projects

            fonda added a comment -

            Wow, this still hasn't been worked on?

            fonda added a comment - Wow, this still hasn't been worked on?

            23ef3e30d63c - this doesn't seem to be a duplicate to me. This issue is asking for the Comment Visibility feature to be available at all for team-managed projects. The other issue is asking to restrict who can set the visibility of a comment and isn't specific to team-managed projects. 

            Majken Longlade added a comment - 23ef3e30d63c - this doesn't seem to be a duplicate to me. This issue is asking for the Comment Visibility feature to be available at all for team-managed projects. The other issue is asking to restrict who can set the visibility of a comment and isn't specific to team-managed projects. 

            Atlassian Update - March 2023

            After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-12347 – Ability to hide comment visibility on team-managed projects

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - March 2023 After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-12347 – Ability to hide comment visibility on team-managed projects We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            I believe this issue is a duplicate of JRACLOUD-12347 – Ability to hide comment visibility on team-managed projects which has more votes.

            I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!

            Anusha Rutnam added a comment - I believe this issue is a duplicate of JRACLOUD-12347 – Ability to hide comment visibility on team-managed projects which has more votes. I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!

            With this feature, our Company could finally migrate to team-managed projects. 

            Morel Richt added a comment - With this feature, our Company could finally migrate to team-managed projects. 

            Hi - yes, this feature would make my life WAY easier. Can you please add the ability to hide certain comments

            Gregg Reaves added a comment - Hi - yes, this feature would make my life WAY easier. Can you please add the ability to hide certain comments

            Pauline added a comment -

            Indeed I don't understand why there is a difference between the projects managed by Company or Team in terms of private comments.
            It is really a necessary feature

            Pauline added a comment - Indeed I don't understand why there is a difference between the projects managed by Company or Team in terms of private comments. It is really a necessary feature

            fonda added a comment -

            I can't believe this feature isn't included?! Actually, I can believe it.. because it's yet another annoying Atlassian thing that I need to explain to the team and my clients. We made a decision early on which projects should be next-gen and which shouldn't. We stuck to classic (formerly known as classic I guess) for about half of them because there were more features! Now everything is screwed because we have a mix of team and company managed projects, categories/terms that don't even make sense from an admin POV, by the way.

            So.. Please hurry up and implement this. Stop trying to do new and "exciting" stuff! Get the classic functionality right first. I don't understand why that hasn't sunk in for you guys yet.. it's incredibly frustrating!

            fonda added a comment - I can't believe this feature isn't included?! Actually, I can believe it.. because it's yet another annoying Atlassian thing that I need to explain to the team and my clients. We made a decision early on which projects should be next-gen and which shouldn't. We stuck to classic (formerly known as classic I guess) for about half of them because there were more features! Now everything is screwed because we have a mix of team and company managed projects, categories/terms that don't even make sense from an admin POV, by the way. So.. Please hurry up and implement this. Stop trying to do new and "exciting" stuff! Get the classic functionality right first. I don't understand why that hasn't sunk in for you guys yet.. it's incredibly frustrating!

            Also looking for this feature

            Bahaa Badran added a comment - Also looking for this feature

            Also looking for this feature. We've migrated most projects to next gen and give clients access. I'd much rather have this feature back instead of having to kick clients out of Jira for sensitive comments (and reducing $$$ to Atlassian)

            Jason Havenaar added a comment - Also looking for this feature. We've migrated most projects to next gen and give clients access. I'd much rather have this feature back instead of having to kick clients out of Jira for sensitive comments (and reducing $$$ to Atlassian)

              Unassigned Unassigned
              adaluz Angélica Luz
              Votes:
              112 Vote for this issue
              Watchers:
              60 Start watching this issue

                Created:
                Updated: