...
The App will check if all the child items are moved into the last column to offer an action of the parent issue as well.
...
Columns/Swimlanes with multiple values assigned
In most of the cases we allow a single value of Jira field as column/swimlane. So when users move the issue into the column/swimlane it’s straightforward to resolve and assign values.
If you need multiple values → use Column Groups.
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.
Multiple Statuses
| Info |
|---|
Coming soon |
You can assign multiple statuses for columns/swimlanes. OR configuration in settings needs to be turned ON.
...
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
| Info |
|---|
Coming soon |
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.
In Jira versions and components are tied to projects so in case you want to emulate the use case mentioned above you create duplicates of versions, components in all the projects assigned.
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!
Other useful tips & tricks
...
(14) If the issue belongs to Epic an Epic Link will be outlined on the card. Once you click on it Jira standard issue screen will show up with Epic details.
...
🆕 Parent headers for children (e.g. Task for sub-tasks and/or Epic for stories)
(15) We have a full scale implementation for Jira Parent field. Therefore, we show the parent header for all the children items outline on the board. The classical use cases are:
Task/Story headers for sub-tasks (similar for Jira boards)
Epic headers for tasks/stories
But also could be Initiatives headers for Epics if configured appropriately.
...
❗ Rename “Others” column or swimlane
...