This repository was archived by the owner on Nov 18, 2021. It is now read-only.
Add explicit +1 feature for issues that isn't a comment #9
Description
Often people post github issue comments like 👍 just so that they can get notified when there are updates, and to indicate that they are also interested in an issue.
It'd be nice if they could just click a thing to do that, without posting a comment that emails everyone else uselessly. It could even put the 👍 comment on the page for cute factor if you feel that's important, but without emailing everyone.
For bonus points, let the project maintainers sort the issues list by the number of votes.
Then the 👍 behavior would be useful, rather than spammy.
Update: (there's a Change.org petition for this now](https://www.change.org/p/github-inc-add-voting-functionality-for-github-issues)
Activity
ericf commentedon Jun 4, 2013
+1
isaacs commentedon Jun 4, 2013
@ericf I see what you did there. ;P
sarahhodne commentedon Jun 4, 2013
Such a button already exists:
It might be made more prominent, though.
polotek commentedon Jun 4, 2013
@henrikhodne I'm not sure if people think of watches as an indicator of importance on issues. To me it just means I want to get emails about new comments. It can probably be repurposed to have more meaning though.
imakewebthings commentedon Jun 4, 2013
@henrikhodne I think what @isaacs wants is a distinction between watchers and a vote of support for the ticket. The Chrome bug tracker does this with "starring" an issue. They may be an interesting case to study because despite that feature they still get a ton of +1 style comments. I think in part because the star is not featured prominently, not explained in any way inline, and generally is not a good representation of what it means.
sarahhodne commentedon Jun 4, 2013
Ah, sorry, I missed that there were two parts to the issue, I only read "make a button so we don't have to comment 👍 to get notifications".
isaacs commentedon Jun 4, 2013
@henrikhodne Yeah, also, there's no way to sort the issues list by the number of watchers, and maybe it could be set up so that the watch link is closer to the "comment" button, and a sort option in the issues list, or a variety of other potential approaches. It would also be nice to not send us all an email for comments that are just an emoticon, maybe. I'm not sure the best way to do this, but it seems like the functionality and data is there, and some relatively minor adjustments could make it much more useful.
dresende commentedon Jun 5, 2013
+1
jsocol commentedon Jun 5, 2013
Is there any way to expose the number of watchers? "Participants" only includes people who comment.
+1 to the 👍 button, though if nothing else, at least in the short term, saying "6 participants and 18 watchers" would be helpful.
jzaefferer commentedon Jun 11, 2013
On Chromium, maintainers are suspicious of issues that get a few dozen stars within a day, blaming the reporter to have a "huge twitter following".
polotek commentedon Jun 12, 2013
Ha, does that somehow make the data less valid?
On Tue, Jun 11, 2013 at 3:15 PM, Jörn Zaefferer notifications@github.comwrote:
Marco Rogers
marco.rogers@gmail.com | https://twitter.com/polotek
Life is ten percent what happens to you and ninety percent how you respond
to it.
zbynekwinkler commentedon Sep 19, 2013
👍
patcon commentedon Sep 19, 2013
Can we separate this out into separate issues? As it stands, I want to express my support for some things mentioned here, but some of it feels like feature creep.
Here's what I see for issue candidates:
I want a way to watch a thread without needing to comment/+1DONEDid I miss anything here?
fgrehm commentedon Sep 19, 2013
We used to have "upvotes" or something similar in a remote past but it ended up getting removed.
From http://blog.leahculver.com/2009/04/github-issues.html
carols10cents commentedon Oct 24, 2013
OR sort issues by 👍 votes, if that functionality is made independent from watching. People might want to leave a 👍 to indicate that they're experiencing that issue too, or they agree with the idea, but don't want to get notifications-- I suppose it's up for debate which number would be a better metric for user pain/need.
364 remaining items
rummik commentedon Mar 21, 2016
@TPS I don't think it should be closed off until we have a way to sort issues by reactions, since that can be considered crucial to a voting system
dmitshur commentedon Mar 21, 2016
@rummik The original issue title is "Add explicit
+1feature for issues that isn't a comment". In the description, it mentions voting/sorting as a bonus:So this issue being closed is quite fair. There's issue #600 that tracks ability to sort issues by votes, etc.
rummik commentedon Mar 21, 2016
@shurcooL My response was was in reference to the Change.org petition that was mentioned by TPS. I agree that this issue should be closed, since reactions do fulfill the issue text
TPS commentedon Mar 22, 2016
@rummik Just put up another petition for that.... 😄
TPS commentedon Mar 24, 2016
All you sorting-by-±1 gripers can rest easy now. To quote (myself 😜) from #600 (comment):
joffrey-bion commentedon Mar 24, 2016
I would not say this is solved. There is still no actual issue upvoting. Just reactions to comments. I don't need reactions, I would like a voting system by issue. I'd like to sort my issues by upvotes minus downvotes count. What is preventing such a simple thing to happen? Is it much more complex than it sounds like?
mitar commentedon Mar 24, 2016
Are those reactions exposed through the API? If so, then you can create any dashboard computing and sorting you want.
sergei-ivanov commentedon Mar 24, 2016
@TPS: I am afraid, it still does not cut it. Hence the petition will remain in place.
howardroark commentedon Apr 2, 2016
This project could help satisfy this want in the short term ... https://gitsup.com/isaacs/github :)
TPS commentedon Apr 9, 2016
@sergei-ivanov & all other gripers: If you have a problem with closing this issue as solved, I'll bet y'all will hate #640. Check it out & let me know what you think. 😜
vsiegel commentedon Jun 5, 2016
I'm clearly opposed to per comment voting, because of the clutter;
But it seems useful to be able to state that an issue is important to one person more,
i.e. me, experiencing it too.
For this, the way launchpad.net does it seems to be brilliant:
Assuming you are logged in and have at least minimal write access
to the system, directly after registering:
There is a link text
This bug affects 109 people, but not you. (Edit)
with a pop up
Does this bug affect you?
Yes, it affects me
No, it doesn't affect me
Selecting "Yes...: adds one and changes the link text to
This bug affects you and 110 other people (Edit)
The UI when logged in is shown in the next two screen shots:
If you are not logged in, the message reads:
This bug affects 109 people, but not you
which is not linked and has no edit button - but somehow suggests that you may
edit it when logged in.
I think it's important that all this does not even resemble a "+1" or "like".
It's technically very similar, but the psychological model is quite different, which makes me hope it does not provoke the same unwanted behavior by analogy.
For full context, see example top left, either logged in or not.
dmitshur commentedon Jun 5, 2016
@vsiegel That link results in 404 for me. Perhaps one needs to be logged in to see it. Maybe should post a screenshot too.
vsiegel commentedon Jun 5, 2016
@shurcooL
Right - first, I was logged in, which changes that part of the UI; I will extend the above comment to explain.
Also, - second part -: I somehow had added an additional character "l" (small L) at the end of the of the URL, which broke it, sorry. Corrected.