Discussion Polls
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal by @DouweM
With award emoji on issues, merge requests and comments, people can share their sentiment about the post. Since each emoji has a counter, they can also be used to democratically decide on a multiple choice question by asking users to award a specific emoji for a specific option. After a certain amount of votes has been amassed, the award emoji counts ("votes") can then be used to decide on the question.
We want to make this feature a first class citizen and an encouraged use of award emoji, instead of a clever hack. To this end, we:
- introduce a new syntax to define votable options in GitLab Flavored Markdown:
- [:pear:] Option, keep track of these votable emoji, and remove the square brackets from the rendered result (requires a new Banzai filter); - automatically show the award emoji buttons for these options below the post (issue/MR/comment), like we currently do with
👍 and👎 ; - show bars representing the relative amount of votes inside the post ("Full C" in the mockup below) (requires a new post-processing Banzai filter, and ~Frontend work);
- expose the options, with emoji, label, count, and percentage, in the API
Original issue description
This idea came from our slack chat: https://gitlab.slack.com/archives/general/p1478537176005140
like a task list, but shows a bar chart after each item based on the emoji responses
- :emoji: Description wouldn't work as people may want to use emoji to give a status to a list where checkboxes aren't sufficient: usecase
Proposal
- [:emoji:] Description
Because the emoji will be the button and that syntax will not conflict with existing use cc: @DouweM
It would work in tandem with the award emoji, but would automatically show the empty award emoji at the bottom, making it easier to vote and possible for the poll creator to vote as well.
- [:pear:] Option 1 short
- [:banana:] Option 2 looooooong
- [:grapes:] Option 3 shrt
- [:pineapple:] Opt 4 Would result in: (mocked various options up ;) to gauge reactions )
Still left to do:
-
if this is done, it should be added to the markdown documentation
Perhaps possible ~"Community Contribution" ?