Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-14131

Upvoting or "plus one" button for comments on issues.

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

      In the same vein as BCLOUD-3674, it would be good to be able to indicate appreciation for a specific comment on an issue, to avoid low value posts that contain little more than +1.

      So basically Github's reactions, with the same rationale, but I would implement it a little differently. Let each user have one reaction, which could be any emoji. A list of emoji would appear at the bottom of a comment, sorted by number of reactions. Clicking the emoji would show usernames. In the odd case where there are lots of reactions, the tail of lesser used emoji could be elided, limiting to a single row of graphics.

      While less can sometimes be more, I think Github's choice of emoticons is poor. I could settle for just two, one positive and one negative, if allowing all seems uncouth.

            [BCLOUD-14131] Upvoting or "plus one" button for comments on issues.

            Atlassian Update - August 2, 2021

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature 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!

            Matthew Hunter added a comment - Atlassian Update - August 2, 2021 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature 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!

            Hi Travis,

            The Atlassian Editor - which is a new comment editor that we'll be rolling out across Bitbucket and our other products soon - will actually have emoji reactions as a feature. So this isn't too far off, actually!

            Alastair

            Alastair Wilkes added a comment - Hi Travis, The Atlassian Editor - which is a new comment editor that we'll be rolling out across Bitbucket and our other products soon - will actually have emoji reactions as a feature. So this isn't too far off, actually! Alastair

              Unassigned Unassigned
              cca2f2b2e5e4 travisfw
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: