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

      It would be good if moderators or authors had the ability to modify defect comments, in the situation where the author of the comment is out of the office and they want all the comments resolved before closing the review.  Although it's true that it's possible to close a review with open comments, that cannot always be done. It would be best to have someone other than the author or moderator update a reviewer's defect category and/or comment in such cases.

            [CRUC-8435] Crucible reviews comment permissions

            Atlassian Update – 10 January 2022

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 10 January 2022 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Kind regards Marek Parfianowicz Development Team Lead

            Marek Parfianowicz added a comment - - edited

            A hack for #2. Use Byteman to modify behaviour of the com.atlassian.crucible.spi.impl.DefaultReviewService#ensureCommentAuthoredBy method (return without throwing an exception). See https://confluence.atlassian.com/fishkb/enable-byteman-for-additional-logging-in-fisheye-and-crucible-943956769.html and https://downloads.jboss.org/byteman/4.0.8/byteman-programmers-guide.html

            Marek Parfianowicz added a comment - - edited A hack for #2. Use Byteman to modify behaviour of the com.atlassian.crucible.spi.impl.DefaultReviewService#ensureCommentAuthoredBy method (return without throwing an exception). See https://confluence.atlassian.com/fishkb/enable-byteman-for-additional-logging-in-fisheye-and-crucible-943956769.html and https://downloads.jboss.org/byteman/4.0.8/byteman-programmers-guide.html

            Marek Parfianowicz added a comment - - edited

            In com.atlassian.crucible.spi.impl.DefaultReviewService#updateComment(com.atlassian.crucible.spi.PermId<com.atlassian.crucible.spi.data.CommentData>, com.atlassian.crucible.spi.data.GeneralCommentData):

            requireOpenReviewPermission(UserActionManager.ACTION_COMMENT, comment.getReview()); // 1
            ensureCommentAuthoredBy(comment, getEffectiveUser()); // 2
            updateComment(newContent, comment);
            

            1 - requires 'Comment' permission (Administration > Permission schemes)
            2 - requires that user is an author of the comment - it cannot be disabled right now

            Marek Parfianowicz added a comment - - edited In com.atlassian.crucible.spi.impl.DefaultReviewService#updateComment(com.atlassian.crucible.spi.PermId<com.atlassian.crucible.spi.data.CommentData>, com.atlassian.crucible.spi.data.GeneralCommentData): requireOpenReviewPermission(UserActionManager.ACTION_COMMENT, comment.getReview()); // 1 ensureCommentAuthoredBy(comment, getEffectiveUser()); // 2 updateComment(newContent, comment); 1 - requires 'Comment' permission (Administration > Permission schemes) 2 - requires that user is an author of the comment - it cannot be disabled right now

              Unassigned Unassigned
              kgrier kitkat (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: