Allow to sort tasks by number of tokens
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• flimport
	Jun 13 2014, 7:10 AM

Description

There are two reports about votes and searches, but I want to document a specific use case: listing bugs by number of votes. For instance, in MediaWiki we have a very hard time convincing people to upgrade, and the best selling point is always showing that we fixed stuff people cared about.

https://www.mediawiki.org/wiki/Manual:Upgrading#Why_upgrade.3F includes a link "See also the list of the most voted fixed issues", we'll need a way to do the same on phabricator (including old data, of course).

Details

Reference: fl414

Related Objects
Search...

Status	Assigned	Task
Resolved	Qgil	T553 Engineering Community team goals for October 2014
Resolved	Qgil	T174 Launch Wikimedia Phabricator Day 1
Resolved	Qgil	T175 Nominate a team in charge of deploying and maintaining Wikimedia Phabricator code
Resolved	• RobLa-WMF	T17 Allocate resources for the migration and maintenance
Resolved	Qgil	T19 Define which features existing in our current tools are really missing in Phabricator
Resolved	Qgil	T15 Migrate Bugzilla to Phabricator
Resolved	Aklapper	T22 Identify features Bugzilla users would miss in Phabricator
Resolved	Qgil	T251 Allow to sort tasks by number of tokens
Declined	• chasemp	T88 Phabricator lacks a feature like Bugzilla's "vote"
Duplicate	Aklapper	T390 Inform users that their Bugzilla tag entries and votes will not be transfered to Phab
Resolved	Aklapper	T497 Deprecation of Bugzilla personal tags
Resolved	Aklapper	T618 Send two email notifications to active Bugzilla users asking them to join Phabricator
Resolved	• chasemp	T572 Determine the fate of comment metadata from legacy systems in phabricator.wikimedia.org
Resolved	• chasemp	T552 https://bugzillapreview.wmflabs.org/ migration preview instance
Declined	• chasemp	T688 Unhandled Exception "HTTPFutureCURLResponseStatus" when running query in Bugzilla test import instance
Resolved	• chasemp	T685 Preview: Incorrect comment authors displayed
Duplicate	• chasemp	T689 Closed ticket imported from Bugzilla shown as open in Phab preview instance
Declined	• chasemp	T686 Incorrect status for imported Bugzilla ticket in Preview Instance
Invalid	• chasemp	T692 Remove unnecessary applications in bugzillapreview
Duplicate	• chasemp	T691 Bugzilla migrated projects and tasks must be Visible To Public
Resolved	Qgil	T695 Severity information is not being migrated
Resolved	• chasemp	T702 Files migrated that (apparently) are not attached to tasks

Event Timeline

aklapper wrote on 2014-06-15 12:47:39 (UTC)

I'm not convinced that the effort (importing votes data) or UI clutter (having some hidden votes field) is worth it to be able to provide a list of fixed tickets that had a number of votes.

Are there more usecases?

Nemo_bis wrote on 2014-06-18 20:20:01 (UTC)

Giving an overview of what's happening in a project that is worthwhile seems to me the whole point of a "project management tool", which AFAIK phabricator aspires to be.
The functionality above needs to be available, in a way or another: this is out of question; but of course we might decide that it's fine to be forced by phabricator to do additional work and have it on a wiki instead of bugzilla.

You asked the same question in the other task so I replied there http://fab.wmflabs.org/T150#25

aklapper wrote on 2014-06-26 10:13:08 (UTC)

In T414#8, @Nemo_bis wrote:

Giving an overview of what's happening in a project that is worthwhile seems to me the whole point of a "project management tool", which AFAIK phabricator aspires to be.

Do you have an example how ''what's happening in a project'' is related to votes in Bugzilla? I completely miss the connection. (In theory, votes might influence which tasks gets fixed or prioritized. In reality I don't see that in Bugzilla.)

this is out of question

It isn't. If nobody uses votes as a source of input anyway, there's no need to support such functionality or even allow sorting by them. In any case, we need to decide on T150 first before we can continue with this item anyway.

aklapper wrote on 2014-06-26 13:02:51 (UTC)

Found https://secure.phabricator.com/T3611#10 :

You can view the objects with the most tokens here, although this currently includes closed/resolved objects and includes objects of all types

See http://fab.wmflabs.org/token/leaders/

I've asked upstream if one could exclude closed tickets plus filter by type of item.

aklapper wrote on 2014-06-26 13:57:13 (UTC)

See https://secure.phabricator.com/T3611#22 - basically WONTFIX upstream as the UI would be too complex. If we explicitly wanted Voting (not tokens) we can file a wishlist item, but it's low priority as upstream isn't convinced of the value it brings. And I share that sentiment.

Qgil edited projects, added Phabricator; removed Wikimedia Phabricator Maintenance.Sep 19 2014, 10:32 AM

(including old data, of course).

We are not migrating votes from Bugzilla. If we still want to pursue this feature, it should be based on the number of tokens.

In T251#3188, @flimport wrote:

aklapper wrote on 2014-06-26 13:57:13 (UTC)

See https://secure.phabricator.com/T3611#22 - basically WONTFIX upstream as the UI would be too complex. If we explicitly wanted Voting (not tokens) we can file a wishlist item, but it's low priority as upstream isn't convinced of the value it brings. And I share that sentiment.

Closed Wontfix upstream, removed from #phabricator.org here.

Qgil removed a project: Phabricator (Upstream).Sep 30 2014, 9:52 PM

Qgil set Security to None.

Qgil moved this task from To Triage to Need discussion on the Phabricator board.

Qgil edited projects, added Phabricator (Upstream); removed Phabricator.Oct 22 2014, 10:40 PM

Liuxinyu970226 subscribed.Nov 17 2014, 10:32 AM

Nemo_bis moved this task from Backlog to Need Discussion on the Phabricator (Upstream) board.Nov 28 2014, 6:16 PM