Now that #1304550: Display count of issue followers when viewing an issue has landed, I think it would be a good idea to add this stat to the issue page list so issues can be sorted by # of followers...
BUT, that is going to add another column to the mix, which is already a bit large in the column count.
SO, one thought I had was to remove # of replies to add # of followers.... not sure if I like that idea, though.

Comments

webchick’s picture

Yeah, don't really like that idea, but I agree this would be great. Maybe a column only on the "advanced search" issue queue views?

Dane Powell’s picture

I would support this idea as-is. Alternatively, could you combine the Replies column with followers? e.g. "Replies/followers: 4/9" or "Replies (followers): 4 (9)"

Once / if issue voting goes live, issue vote counts could replace the number of followers.

tim.plunkett’s picture

Combining them would prevent the ability for them to be sorted.

dww’s picture

Issue tags: +flag integration

Sorry folks. Until #949372: Port issue views to Search API so we can have a performant backend is done I think nnewton will kill me if I do this. Sorting by follower count will completely kill the performance of these queries due to how flag works. Unless of course we denormalize this data into {project_issue_nodes}, but ugh. If we go that far, it's not clear what's the point of using flag.module at all since we have to duplicate so much of what it's doing, etc. :(

I'll try to get his input on this, but I think he's going to veto it.

klonos’s picture

...one thought I had was to remove # of replies to add # of followers...

For issues filed long before #34496: [meta] Add Flag module to allow users to subscribe/unsubscribe without posting a comment it might so happen that the number of followers (formerly known as "subscribers") is almost the same as the number of replies anyways :P

Being able to sort issues by followers would help us get an idea of which features are hot. Pretty much similar to what we did in Submit and vote on your Drupal.org ideas!. Now, I am aware that not all followers of an issue are necessarily "voting" for it, but still...

dww’s picture

Yeah, to be clear: I understand why this is useful and a Good Thing(tm) from a collaboration tools perspective. I just wear multiple hats. Taking off my "make our tools really slick for our developers" hat and putting on my "make sure our tools don't melt our infrastructure" hat forces me to sing a different tune, that's all. And again, there *are* ways to do this that don't melt our infrastructure, but they're more complicated than "click this together in views and deploy it".

klonos’s picture

Fair enough. Then let's see if we can work this out after we've implemented #949372: Port issue views to Search API so we can have a performant backend or something similar that (hopefully) scales performance-wise.

geerlingguy’s picture

Voicing my support here too... I don't know any good solution to the problem of adding yet another column to the issue queue/tracker, though. I'd rather dump a column or two before adding another :-/

drumm’s picture

Version: 6.x-1.x-dev » 7.x-2.x-dev
Issue summary: View changes

#2925877: Add sortable Followers column to project issues lists is the best issue to follow for implementation on Drupal.org. Drupal.org does not use project_issue’s default Views, instead it uses Search API.

This issue is still relevant for the default Views in project_issue module.

arlinsandbulte’s picture

Looks like this was implemented on D.O (#2925877: Add sortable Followers column to project issues lists)
Can/should this issue be closed?

drumm’s picture

No, it should stay open. See #9.

arlinsandbulte’s picture

OK, that is kinda what I thought.