• 1
    • We collect Jira Service Desk 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.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      As a workaround to https://jira.atlassian.com/browse/JSD-270
      Service Desk administrators usually set the Browse permission to the Service Desk project allowed to Anyone, doing so, customers will be able to see request reported by other customers.

      However, the "Anyone" permission will make visible the internal comments, since these internal comments are JIRA standard comments, and users will access in the issue should be able to see.

      As a Service Desk Administrator, I would like to hide my internal comments, even from users with browse permission.

            [JSDSERVER-2143] Internal Comment should not be visible by anonymous user

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3010875 ] New: JAC Suggestion Workflow 3 [ 3648262 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665250 ] New: JAC Suggestion Workflow [ 3010875 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2324556 ] New: Confluence Workflow - Public Facing v4 [ 2665250 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2053687 ] New: JSD Suggestion Workflow - TEMP [ 2324556 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2048859 ] New: JSD Suggestion Workflow [ 2053687 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1279453 ] New: JSD Suggestion Workflow - TEMP [ 2048859 ]
            jonah (Inactive) made changes -
            Description Original: As a workaround to https://jira.atlassian.com/browse/JSD-270
            Service Desk administrators usually set the Browse permission to the Service Desk project allowed to Anyone, doing so, customers will be able to see request reported by other customers.

            However, the "Anyone" permission will make visible the internal comments, since these internal comments are JIRA standard comments, and users will access in the issue should be able to see.

            As a Service Desk Administrator, I would like to hide my internal comments, even from users with browse permission.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-2143].
              {panel}

            As a workaround to https://jira.atlassian.com/browse/JSD-270
            Service Desk administrators usually set the Browse permission to the Service Desk project allowed to Anyone, doing so, customers will be able to see request reported by other customers.

            However, the "Anyone" permission will make visible the internal comments, since these internal comments are JIRA standard comments, and users will access in the issue should be able to see.

            As a Service Desk Administrator, I would like to hide my internal comments, even from users with browse permission.

              Unassigned Unassigned
              psouza Pedro Souza
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: