The team in charge of a project may need to vote for something (much like a poll, actually). Typical case : a design decision.

Adding such a feature seems to me quite orthogonal to current features, so this probably doesn't change redmine design, nor would it bloat redmine source code

The idea is not to propose a poll like seen on most website, which are used , but rather a tool do make decision. That's why i've called that 'voting' and not 'polling'. For example, there could be several votes at some given moment, and those votes would have a dedicated tab, not appearing on the main project page.

Note that this is different from #1011, which is 'voting for bugs', or #1158 (more like 'random poll on websites', not clear what people want, standalone or linked to an issue). I hope I describe it here clearly enough so that there's no ambiguity on the intended use.

Here's a description of how i see this (subject to comment, of course)

Specifications¶

There's a module called 'Voting' that you can select on a per-project basis. I guess that it being a plugin is an implementation issue.

Structure of a vote (db description)¶

• A title (string)
• A description (for example with a link to a wiki page, or to specifiy until when the vote is opened)
• A state (boolean) : opened or closed
• A boolean flag : internal (see below)
• A list of strings, from which voters will select one and only one.

global changes¶

• There's a new permission "Can handle vote"

How it works¶

• Once enabled, roles having the permission "Can handle vote" can add a vote, which by default is 'opened'.
• if the flag internal is set to true, only the members of the project see the vote, and can vote. If set to false, everybody can see/vote. Note that this is different from the 'public' flag of the project. Of course, if the project is private, then there's no point in having a vote with internal=false.
• In any case, only identified people can vote, to facilitate the design.
• When the vote is 'opened', people (everybody or only members, according to the internal flag) can vote and change its vote.
• Roles having the permission "Can handle vote" can close the vote
• When the vote is closed, nobody can vote or change its vote anymore, but the result is still displayed (to everybody or only project members, according to the internal flag).

Examples of votes¶

1. An internal vote for choosing the best library to use for some given requirements.
2. An external vote to ask users which feature they prefer for the next release.

Discussion¶

Maybe instead of using the internal flag, it would be wise to use redmine roles for that, but i'm not sure how to do that.

I don't think it is necessary to specify the date of closing to redmine so that no human intervention is needed.

Future / more features¶

Could be:

• an option to display, or not, the current number of votes and the current result, while the vote is opened
• other fields than just list of strings. For example several lists which one choice in every list, or people entering a number between given min/max values.