# Epic FND-249 - Add support for task voting

Project: Stream workspace foundations
Status: new
URL: https://community.openproject.org/work_packages/FND-249

## Detailed specification

### Motivation and background information

### Acceptance criteria

*   A registered user should be able to quickly add a single vote on their own
    
    *   user name should be saved (votes should not be anonymous), so that users can be eventually contacted for user research
        
*   it should be possible to add votes on behalf of someone (use cases: adding votes on behalf of users / customers)
    
    *   there should be an option to make the customer&#x27;s name public or confidential (seen only by users with a certain role, e.g. internal only)
        
    *   only users with certain privileges should be allowed to do votes on behalf of someone

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes | 18 |
| List |  |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

It would be nice to be able to vote on issues, and filter on those votes.

This is particularly important for FOSS projects (like this one) where you want to be driven by customer demand, but don’t want a bunch of “+1 Me Too” comments.

Example: http://www.redmine.org/plugins/redmine\_vote\_plugin
