...
But sometimes you do want to have an option to assign multiple values. In such a case you have 2 challenges:
what to show in column/swimlane - issues that has all values assigned? or at least one?
To address this we have the following configuration in board settings:
...
what to do when user moves issue into column/swimlane - try to assign all the values? or play smart and see what can you assign?
For the later see use cases below.
...
You can assign multiple statuses for columns/swimlanes. OR configuration in settings needs to be turned ON to allow such assignment.
...
🧐 Since the issue can’t sit with 2 statuses only one could be assigned. When you will be moving issue into such a column/swimlane the App will analyse the workflows of the projects attached to the board and specific project for the issue and shortlist the possible statuses from the ones assigned to column/swimlane.
If the candidate is “One Only“ the App will assign appropriate status on move. If there are couple of available options the App will show a dialog to select.
...
Multiple Versions, Components, Labels and other multi-select fields
This is a good use case for cross-project components and versions when different teams develop in different Jira projects but have a unified set of versions and components.
...
Now let’s say you brought issues from those projects to out board and you want to use mapping to assign version/component. So you create columns/swimlanes and map “avatars“ for proper cross-project version/component to it.
🧐 In the past we would deny move to such Column/Swimlane (for obvious reasons). But with recent functionality release the App will check the project key for the issue and assign only appropriate version/component.
Enjoy it!
Append values on move vs override
If OR configuration is on for the multi-values columns/swimlanes (but statuses) you can decide if you want to append you new value when you move (keeping the old ones) or override (removing the old ones).
...
Other useful tips & tricks
...