Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-12347

Only certain groups or users should be able to set the "Viewable by" for comments

    • 4
    • 33
    • 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.

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

      If there's a way to restrict only certain groups or users to set the "Viewable by" value of a comment..

        1. screenshot-1.png
          screenshot-1.png
          48 kB
        2. screenshot-2.png
          screenshot-2.png
          309 kB

            [JRACLOUD-12347] Only certain groups or users should be able to set the "Viewable by" for comments

            Anusha Rutnam added a comment - - edited

            Update 25 August 2023

            After further discussion here on JSWCLOUD-18778 – Comment restriction for team-managed (formerly next-gen) projects we've determined that these issues were not duplicates and this one does not refer to team-managed projects. Apologies for the confusion caused.

             

            ***

            Comments can be restricted in company-managed Jira Software and Jira Work Management projects.

            Would the watchers of this issue be ok with me changing its title to "Ability to hide comment visibility on team-managed projects"? That way I could recommend that the existing watchers of JSWCLOUD-18778 – Comment restriction for team-managed (formerly next-gen) projects come and watch this instead. 

            Anusha Rutnam added a comment - - edited Update 25 August 2023 After further discussion here on JSWCLOUD-18778 – Comment restriction for team-managed (formerly next-gen) projects we've determined that these issues were not duplicates and this one does not refer to team-managed projects. Apologies for the confusion caused.   *** Comments can be restricted in company-managed Jira Software and Jira Work Management projects. Would the watchers of this issue be ok with me changing its title to "Ability to hide comment visibility on team-managed projects"? That way I could recommend that the existing watchers of JSWCLOUD-18778 – Comment restriction for team-managed (formerly next-gen) projects come and watch this instead. 

            This is a serious security concern for us at John Deere as we have external partners using our Jira platform. If we cannot hide certain comments in certain projects for them, we really would have to re-consider our use of Jira

            If you need any further information, please get in touch with me

            Fahad Khan added a comment - This is a serious security concern for us at John Deere as we have external partners using our Jira platform. If we cannot hide certain comments in certain projects for them, we really would have to re-consider our use of Jira If you need any further information, please get in touch with me

            We are moving to the Jira Cloud. We need this feature turned ON. On Jira Server platform, we use the "Default Comment Security" to hide some Issue comments from our external partners. Unfortunately, this plugin is not available on the Jira Cloud platform.

            Trung Pham added a comment - We are moving to the Jira Cloud. We need this feature turned ON. On Jira Server platform, we use the "Default Comment Security" to hide some Issue comments from our external partners. Unfortunately, this plugin is not available on the Jira Cloud platform.

            Agree - this seems an obvious option to be able to have. Please consider adding it.

            Helen Buchanan added a comment - Agree - this seems an obvious option to be able to have. Please consider adding it.

            This is greatly needed

            Nick Perkins added a comment - This is greatly needed

            At least there is an add-on for JIRA Server that would help,  there is no solution for setting a default visibility on JIRA Cloud.  We really need this.

            Lorraine Gorman added a comment - At least there is an add-on for JIRA Server that would help,  there is no solution for setting a default visibility on JIRA Cloud.  We really need this.

            Greg Kastl added a comment - - edited

            All I need is another function here in the "Comments Permissions" section, titled "View Comments":

            Then, I would limit this down so that my client cannot see the developers' comments on a ticket. Pretty please?

            Greg Kastl added a comment - - edited All I need is another function here in the "Comments Permissions" section, titled "View Comments": Then, I would limit this down so that my client cannot see the developers' comments on a ticket. Pretty please?

            This feature is very useful when using JIRA Service Desk dedicated to customers. JIRA Service Desk is too restrictive (no way to show some of the comments), unless I am mistaken.

            PASCAL CALLEGARI added a comment - This feature is very useful when using JIRA Service Desk dedicated to customers. JIRA Service Desk is too restrictive (no way to show some of the comments), unless I am mistaken.

            I have a question:
            Using JS will only help to set a comment's security level when manually adding a comment on the ticket. What about comments which are automatically added, e.g. by mail handlers?

            MINT Operations added a comment - I have a question: Using JS will only help to set a comment's security level when manually adding a comment on the ticket. What about comments which are automatically added, e.g. by mail handlers?

            My Kro added a comment - - edited

            The old hacks don't work in JIRA 5 because it introduces the "quick edit" popup screens and uses new div names.

            After way more fscking about than I should have to do, I've figured out how to do this for JIRA 5.1.4.

            Add this to your announcement banner:

            <script> (function($){ JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function (e, context)

            { AJS.$('div.security-level').hide(); }

            ); })(AJS.$); </script>

            And then add this if you don't have an announcement (ie. hide the banner itself):

            <style> .alertHeader

            {display: none}

            </style>

            Apologies for the single-line density but the comment field wouldn't let me use a nicer format.

            Hope this helps someone else.

            My Kro added a comment - - edited The old hacks don't work in JIRA 5 because it introduces the "quick edit" popup screens and uses new div names. After way more fscking about than I should have to do, I've figured out how to do this for JIRA 5.1.4. Add this to your announcement banner: <script> (function($){ JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function (e, context) { AJS.$('div.security-level').hide(); } ); })(AJS.$); </script> And then add this if you don't have an announcement (ie. hide the banner itself): <style> .alertHeader {display: none} </style> Apologies for the single-line density but the comment field wouldn't let me use a nicer format. Hope this helps someone else.

              Unassigned Unassigned
              yuenchi.lian Yuen-Chi Lian [Atlassian]
              Votes:
              140 Vote for this issue
              Watchers:
              70 Start watching this issue

                Created:
                Updated: