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

Make it more obvious that the restriction on comment visibility does not apply to attachment

    • 1
    • 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.

      If I add an attachment by clicking on the "Attach file to this issue" link, I see the attached screen. At the bottom, there is a drop-down menu for limiting who can see the attachment and comment. Right? Well, it only hides the comment. The attachment is viewable by all users who have permission to view that issue, even if you change the value from "All Users" to a smaller group of users. In the screenshot, the attachment should not be seen by users who are not in the G2 Developers group. But they are.

      If attachments cannot be hidden from certain groups, then remove the drop-down menu. But since the drop-down menu exists, I expect it to apply to both the attachments and the comment.

            [JRACLOUD-10992] Make it more obvious that the restriction on comment visibility does not apply to attachment

            Atlassian Update - January 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new features policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Anusha Rutnam added a comment - Atlassian Update - January 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new features policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

            Georg DE added a comment - - edited

            I have exactly the opposite symptom: Attachements are visible for only some users and I can neither anticipate the visibility when uploading nor check visibility for existing attachments. Hence, repeatedly, some people are cut off from information they shall have. A clear solution IMHO must be two-fold: When uploading an attachment, a clear statement shall be made who will be able to see (i.e. enable users to anticipate results of their action), and for existing attachments, users need some clear information about visibility state. I assumed the latter exists, but found out the currently shown yellow banner and the pad lock icon

            (Edit: I cannot see my own attachment, maybe others have the same issue, hence I uploaded to https://i.postimg.cc/HWS2K95B/Jira-5-lock-symbol-has-nothing-to-do-with-visibility-of-attachements-or-related-comments.png)

            are NOT about visibility of the attachment and are also NOT about visibility of comments that are using/referencing the attachment (i.e. it is NOT the logic "if an attachment is used in no comment or only in visibility restricted comments, it won't be visible for all users and lock appears"). I did not yet find out what the padlock icon indicates and documentation  pages like https://support.atlassian.com/jira-software-cloud/docs/switch-between-the-strip-and-list-view-for-attachments/ etc. do not mention it at all  

            Georg DE added a comment - - edited I have exactly the opposite symptom: Attachements are visible for only some users and I can neither anticipate the visibility when uploading nor check visibility for existing attachments. Hence, repeatedly, some people are cut off from information they shall have. A clear solution IMHO must be two-fold: When uploading an attachment, a clear statement shall be made who will be able to see (i.e. enable users to anticipate results of their action), and for existing attachments, users need some clear information about visibility state. I assumed the latter exists, but found out the currently shown yellow banner and the pad lock icon (Edit: I cannot see my own attachment, maybe others have the same issue, hence I uploaded to https://i.postimg.cc/HWS2K95B/Jira-5-lock-symbol-has-nothing-to-do-with-visibility-of-attachements-or-related-comments.png ) are  NOT about visibility of the attachment and are  also NOT about visibility of comments that are using/referencing the attachment (i.e. it is NOT the logic " if an attachment is used in no comment or only in visibility restricted comments, it won't be visible for all users and lock appears "). I did not yet find out what the padlock icon indicates and documentation  pages like  https://support.atlassian.com/jira-software-cloud/docs/switch-between-the-strip-and-list-view-for-attachments/  etc. do not mention it at all  

            Andre V. added a comment -

            If we can't get JRA-3893, this is the minimum I expect. But to be honest, after 10 years, I don't believe it will ever happen.

            Andre V. added a comment - If we can't get JRA-3893 , this is the minimum I expect. But to be honest, after 10 years, I don't believe it will ever happen.

            Jim Baker added a comment -

            I vote for this, too.

            Jim Baker added a comment - I vote for this, too.

            Updated the summary to more accurately depict the fix.

            Scott Farquhar added a comment - Updated the summary to more accurately depict the fix.

              Unassigned Unassigned
              b7ebfa0332d2 Randy Devol
              Votes:
              9 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: