...
| Info |
|---|
You can also configure columns/swimlanes by Epics and Stories. |
Parent Header
| Tip |
|---|
Check also how you can configure “Parent Header“ for the issues - https://releasemanagement.atlassian.net/wiki/spaces/ASPT/pages/875692462/Board+dynamics#%F0%9F%86%95-Parent-headers-for-children-(e.g.-Task-for-sub-tasks-and/or-Epic-for-stories) - as alternative to swimlanes/columns by Parent. |
You might decide to show a clickable Parent Header for your issues. This is very useful if you go beyond standard Sub-task > Story > Epic hierarchy and can show story header for sub-tasks and Epic link by standard tools.
...
By clicking on Parent Header toggle you turn on the clickable header (meaning you will see an issue dialog when you click on it) for your issues.
You might also decide to customize the levels of hierarchy where you want to show this header, namely:
-1 stands for Sub-tasks
0 stands for Stories & Tasks
1 stands for Epics
2+ is usually custom to your setup (e.g. Features > Initiatives > Capabilities)
Cloud | Data Center
| ||||||
|---|---|---|---|---|---|---|---|
 |  |
Update status and Change assignee for Parent right from Column/Swimlane
...
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!
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
In-line creating issues
(8) To create issue on the board click on the "+" inside any cell to popup standard Jira issue creation dialog. Upon creation appropriate values from column/swimlane will be assigned to put issue in the cell selected.
...
Inplace editing (Edit from Card)
No need to open issue dialog to change Assignee, Priority, Status or Estimates. You can now do it inplace from the card.
Priority
...
Status
...
Assignee
...
Estimates
If you have statistics set in Story Points or Remaining Hours you can now change it directly from the card.
...
More options to come shortly.
On the Card
Flagged issues
(10) We have native support for Flagged Issues. Thus we color code them accordingly. Plus you can add/remove the flag directly from the board.
...
💫 Impediment Reason
| Status | ||||
|---|---|---|---|---|
|
TBD
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!
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
In-line creating issues
(8) To create issue on the board click on the "+" inside any cell to popup standard Jira issue creation dialog. Upon creation appropriate values from column/swimlane will be assigned to put issue in the cell selected.
...
Inplace editing (Edit from Card)
No need to open issue dialog to change Assignee, Priority, Status or Estimates. You can now do it inplace from the card.
Priority
...
Status
...
Assignee
...
Estimates
If you have statistics set in Story Points or Remaining Hours you can now change it directly from the card.
...
More options to come shortly.
On the Card
Flagged issues
(10) We have native support for Flagged Issues. Thus we color code them accordingly. Plus you can add/remove the flag directly from the board.
...
💫 Impediment Reason
| Status | ||||
|---|---|---|---|---|
|
Sometimes you want to specify a standard impediment reason why flagging an issue. With our Advanced Feature we let it happen.
At first you need to go to Board Settings to configure lookup - standard or custom field that will be used for impediment reason. We support all
Label
All single-select fields
All multi-select fields
String fields
.. as possible candidates for impediment reason.
...
Once configured you will see a look up on Flag Issue screen to specify.
...
Epic link on the card
(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.
...
🚀 Expand one column
(17) Sometimes you want to give yourself more space on the board to play with uses. To support that we now allow expansion one of the columns.
...
This creates a “backlog-like“ view to play with issues more handy:
...
to give yourself more space on the board to play with uses. To support that we now allow expansion one of the columns.
...
This creates a “backlog-like“ view to play with issues more handy:
...
🌈 Color your board your way - Colors for Columns and Groups
To define your custom colors for Columns or Groups click on Column/Group edit and navigate to Color tab.
Here you can define color or a complete Column/Group as well as per-swimlane configuration.
...
| Info |
|---|
Do not worry about overlying colors for columns/groups and their WIP limits. We will manage such overlying to make the best outlook possible. |
| Include Page | ||||
|---|---|---|---|---|
|