Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-829

Adding Comments - more comment visiblity options instead of just being restricted to 2 options

    • 80
    • 31
    • 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 Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      Atlassian Update – 22 November 2024

      Hi everyone,

      Thank you for your engagement with this suggestion.

      This one gained a significant amount of traction and interest and we are excited to announce that it has been developed and implemented in version 10.2 of JSM.

      To learn more about this feature check out the release notes here: 10.2 release notes

      Kind regards,

      Jim Alexander

      Jira Service Management, Data Center & Server

      Hi,

      I would still like to be able to select from a drop down to hide a comment based on Project Roles with or without JSD being enabled. Only having two options (Internal, Customer) is not enough.

      Thanks
      Darren

          Form Name

            [JSDSERVER-829] Adding Comments - more comment visiblity options instead of just being restricted to 2 options

            Hey everyone,

            Very excited to be bringing JSM comment restrictions in to version 10.2

            You will now be able to further restrict comments to the current users roles and groups.

            Learn more about it here in the: 10.2 release notes

            Jim Alexander added a comment - Hey everyone, Very excited to be bringing JSM comment restrictions in to version 10.2 You will now be able to further restrict comments to the current users roles and groups. Learn more about it here in the: 10.2 release notes

            Any specific reason as to why this feature is not being considered? Seems like a lot of customers are requesting it

            Amit Jambusaria added a comment - Any specific reason as to why this feature is not being considered? Seems like a lot of customers are requesting it

            Please add this as it makes no sense to have a different behavior in JSW vs JSM

            Céline Otjacques added a comment - Please add this as it makes no sense to have a different behavior in JSW vs JSM

            Tim Hailey added a comment -

            +1

            It makes no sense that you can restrict comment visibility to group and project roles in Jira but not JSM. We have many teams asking why we can do this in Jira and not JSM.

            Tim Hailey added a comment - +1 It makes no sense that you can restrict comment visibility to group and project roles in Jira but not JSM. We have many teams asking why we can do this in Jira and not JSM.

            +1

            Attila Nemeth added a comment - +1

            Atlassian Update – 29 December 2022

            Hi everyone,

            Thank you for your engagement with this suggestion.

            After reviewing this ticket we have decided not to consider it at this point in time. We are currently focused on delivering items on the Jira Service Management Data Center public roadmap, which you can view here. We will review this suggestion again in the future, so please continue to vote and watch the ticket, and leave comments if you have particular use cases that you would like to see supported in JSM Data Center.

            Kind regards,

            Charlie Marriott

            Jira Service Management, Data Center & Server

            Charlie Marriott added a comment - Atlassian Update – 29 December 2022 Hi everyone, Thank you for your engagement with this suggestion. After reviewing this ticket we have decided not to consider it at this point in time. We are currently focused on delivering items on the Jira Service Management Data Center public roadmap, which you can view here . We will review this suggestion again in the future, so please continue to vote and watch the ticket, and leave comments if you have particular use cases that you would like to see supported in JSM Data Center. Kind regards, Charlie Marriott Jira Service Management, Data Center & Server

            +1

            Aaron Charles added a comment - +1

            +1

            +1 - Switching from JSW to JSM means that our JSW "Internal to a group" comments are now JSM "EXTERNAL to a group" comments. What was private comments within a support group are now being shared with ALL JSW/Jira users within our company. This has caused many problems. Please implement the same feature that is in JSW Jira into JSM Jira. You're using the same Jira backend so the Jira features should work the same.

            Tim Jedlicka added a comment - +1 - Switching from JSW to JSM means that our JSW "Internal to a group" comments are now JSM "EXTERNAL to a group" comments. What was private comments within a support group are now being shared with ALL JSW/Jira users within our company. This has caused many problems. Please implement the same feature that is in JSW Jira into JSM Jira. You're using the same Jira backend so the Jira features should work the same.

            Status GATHERING INTEREST means: " This suggestion needs more unique domain votes and comments before being reviewed by our team."

            Therefore I want to repeat Royden's question: How many votes are needed before you start work on this ?

            Hartwig Schneider added a comment - Status GATHERING INTEREST mea ns: " This suggestion needs more unique domain votes and comments before being reviewed by our team." Therefore I want to repeat Royden's question: How many votes are needed before you start work on this ?

              fb78834a366d Jim Alexander
              4a5ad1aa092a Darren Pegg
              Votes:
              402 Vote for this issue
              Watchers:
              209 Start watching this issue

                Created:
                Updated:
                Resolved: