I haven't really worked out how tokens are useful but it struck be that the thumbs up and thumbs down tokens would be useful to see on a workboard to help with prioritisation. Is this a supported feature or configurable in any way?
|phabricator/extensions/Sprint : master||removes Tokens from Sprint Card|
- Mentioned In
- rPHSPd01d47ed4176: removes Tokens from Sprint Card
T28: Decide on wanted metrics for Maniphest in kibana
T78617: Decide on "Needs Volunteer" Priority field value in Phabricator
- Mentioned Here
- T88486: Add label support like in Trello
T251: Allow to sort tasks by number of tokens
T899: Unclear what the point of tokens in Phabricator is
T888: List bugs by number of duplicates
Also, how the UI would be. Do you mean to show the number of thumbs up/down tokens in a task? What about other tokens? Maybe the raw amount of tokens a task is accumulating might be useful to make it stand up in a crowded workboard, but I wouldn't read too much in the types of token used.
On a wider (bikesheddier) level, identifying popularity of a task is pretty hard in bug tracking: Number of duplicates (cf. T888)? Number of tokens? Number of subscribers? Number of comments?
The only real use case ive found for them is to draw more attention to certain things. E.g. a card that has sat in code review for too long or a card where a vote of some sort is taking place.
all I'm suggesting is when you rendering the work board these tokens are visible (or at least can be configured to be visible)
Trello has a concept of stickers and these seem similar.
@Aklapper has a point. Tokens were contested at T899: Unclear what the point of tokens in Phabricator is and we kind of agreed to keep them as long as we don't load much meaning on them. Upstream has been also reluctant to give them much relevance, i.e. by postponing/declining features helping to define queries of tasks based on number of tokens, etc.
As much as I like these tokens bringing some colors and impressions to tasks, I also don't think that we should promote them beyond measure. Declining looks like a good idea, yes.
This is done, and it could be part of the Wednesday upgrade if it you agree. Check it here: https://phab08.wmflabs.org/tag/production_test/board/
The problem with tokens now it is that there are not enough of them, and the default ones are not very meaningful. A token could in theory function like a very simple Trello label (see T88486).
One possibility towards this end would be to create a custom image map of colored icon symbols to replace the default tokens.
As said before, I don't think this is a good idea. It has a risk of "tokenizing" discussions. Besides, once a task is committed to a sprint, what is the point of tokens, really? Such tasks are expected to be completed in the short terms, and having these or those or no tokens shouldn't make any difference.
Yes, I know I was the one suggesting to use this feature within the context of the Sprint extension. Sorry, I was mistaken, and I could only see this clearly after Andre's arguments and Christopher's proof of concept.