Content
View differences
Updated by Niels Lindenthal about 5 years ago
# User Problem
## User
_What persona, persona segment, or customer type experiences the problem most acutely?_
* Project manager
* Project member
## Problem
_What problem or job does the user have?_
* There are work packages that have multiple assignees.
* Pair programming on a feature
* Construction work like painting an entire floor.
* Requirements workshop with multiple users
* ....
## Pain
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* Adding custom fields of type user.
* Difficult to understand.
* Not linked with notifcations
* Complex configuration
## Solution
* Allow to add multiple assignees for a work package.
* Adapt grouping by assignees
* Work packages table
* Charts
* Adapt filters
* Adapt cost reports
* ##32579
* Adapt notifications
* Bulk edit
## Out of Scope for the MVC
_What should NOT be in the minimal viable change, and can be considered for future iterations? Why? Please order them by importance._
* Change to the filter: It is not possible to filter for work packages that have multiple assignees (all work packages assigned to Person A AND Person B).
* Allow for multiple assignees by custom actions.
* Adapt bulk edit to allow for multiple assignees
* Group by custom fields of type user
## Differentiation
_What do you believe will differentiate us from the current experience or competitive experiences?_
* Issues tracker
* Redmine does not support this.
* Jira does not support this ([docs](https://confluence.atlassian.com/jira/how-do-i-assign-issues-to-multiple-users-207489749.html)).
## Next iteration
_What is the next solution that would allow us to release meaningful customer value quickly?_
* Calculate duration based on assigned resources. ...
* Multi-project capacity management.
# Launch and Growth
## Measures
_How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?_
* Adoption: Percentage of work packages with more than one assignee. ...
## Messaging
_If you were to write a press release, how would you describe the value to customers?_
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">Headline</th><td class="op-uc-table--cell">Multiple assignees for work packages</td></tr><tr class="op-uc-table--cell"></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">First Paragraph</th><td class="op-uc-table--cell">You can now assign multiple assignees to a workpackge. This is extremely helpful when several persons work on the same work package. </td></tr><tr class="op-uc-table--cell"></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">Customer Quote</th><td class="op-uc-table--cell">We do pair programming here at xxxx. Now we can assign a new feature to a team of two developers.</td></tr></tbody></table></figure> class="op-uc-table--cell"></td></tr></tbody></table></figure>
## Go to market
_How are you planning on getting this into users' hands?_
* Newsletter
* Press release
* In-app announcement
* Blog article
* Social media
## User
_What persona, persona segment, or customer type experiences the problem most acutely?_
* Project manager
* Project member
## Problem
_What problem or job does the user have?_
* There are work packages that have multiple assignees.
* Pair programming on a feature
* Construction work like painting an entire floor.
* Requirements workshop with multiple users
* ....
## Pain
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* Adding custom fields of type user.
* Difficult to understand.
* Not linked with notifcations
* Complex configuration
## Solution
* Allow to add multiple assignees for a work package.
* Adapt grouping by assignees
* Work packages table
* Charts
* Adapt filters
* Adapt cost reports
* ##32579
* Adapt notifications
* Bulk edit
## Out of Scope for the MVC
_What should NOT be in the minimal viable change, and can be considered for future iterations? Why? Please order them by importance._
* Change to the filter: It is not possible to filter for work packages that have multiple assignees (all work packages assigned to Person A AND Person B).
* Allow for multiple assignees by custom actions.
* Adapt bulk edit to allow for multiple assignees
* Group by custom fields of type user
## Differentiation
_What do you believe will differentiate us from the current experience or competitive experiences?_
* Issues tracker
* Redmine does not support this.
* Jira does not support this ([docs](https://confluence.atlassian.com/jira/how-do-i-assign-issues-to-multiple-users-207489749.html)).
## Next iteration
_What is the next solution that would allow us to release meaningful customer value quickly?_
* Calculate duration based on assigned resources.
* Multi-project capacity management.
## Measures
_How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?_
* Adoption: Percentage of work packages with more than one assignee.
## Messaging
_If you were to write a press release, how would you describe the value to customers?_
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head">Headline</th><td class="op-uc-table--cell">Multiple assignees for work packages</td></tr><tr
## Go to market
_How are you planning on getting this into users' hands?_
* Newsletter
* Press release
* In-app announcement
* Blog article
* Social media