Table of Contents | ||||
---|---|---|---|---|
|
...
Name of the board
Permissions (coming soon) - See Permissions Management
Projects to pool Jira issues from
JQL (Board JQL) to filter out the issues
Nave JQL (Board Analytics JQL powered by Nave) to filter out the issues in case there’s a strong reason to have it different from Board JQL
🆕 Hide older than + list of columns
...
Order by to select the field you would like to use for ordering (Rank is default option)
...
Info |
---|
If Story Points or Hours will be selected we will show also statistic on individual issue card. |
🆕 WiP limits to select whether include sub-tasks in WIP limits calculations or not.
Columns and Swimlanes
(4) on “Columns and Swimlanes“ tab you can change configuration of fields used respectively for Columns and Swimlanes. Swimlanes are optional. To remove them choose “-- none -- “ in popup.
...
Allow OR for Columns and Swimlanes with multiple values assigned.
...
The feature is
...
two folds, namely
Visualization purposes when you want to show that issue belongs to multiple columns/swimlanes. While applying WIP limits we will consider only unique issues.
...
Columns/Swimlanes with multiple values assigned. The most interesting cases are multiple statuses, versions, components (the later 2 could be cross-project versions, components), other multi select values. Using OR configuration ones doors to a number of use cases. Please check out the functionality below when the App act very smart:)
...
(4) on “Columns and Swimlanes“ tab you can change configuration of fields used respectively for Columns and Swimlanes. Swimlanes are optional. To remove them choose “-- none -- “ in popup.
...
💯 Keep issues with parent
...
By clicking on Automatically add existing values toggle you will get all the Columns/Swimlanes auto populated automatically based on distinct set of values extracted from Jira issues matching the JQL for the board..
...
How we do it?
We run a JQL applying filter by project selected for the board and board JQL on top
We get a list of Jira issues as a result to outline on the board
We check what are the fields configured for columns/swimlanes
We extract distinct values of these fields values from the Jira issues shortlisted
We create appropriate columns/swimlanes according to the order defined
We map issues to appropriate columns/swimlanes
We do it every time to open or refresh the board
Automatically remove empty columns or swimlanes
...
If you use the above configuration the App will auto create columns and swimlanes for you if there are issues to show.
...
As you progress with your tasks issue might disappear from the board - e.g. your filter might be set to avoid completed issue with last updated > 2 weeks. This might lead to empty columns or swimlanes that will take valuable space on the screen. You can always click on such column/swimlane and remove it from the board. Or you can turn on the configuration in the setting to remove it automatically.
...
Once you define it as JQL drag and drop will obviously won’t be allowed bu could be used as great visualization technique as well as other complementory complementary features.
You can also combine the 2 aproachesapproaches. E.g. Columns maped mapped to properties while swimlanes defined as JQLs. Thus you can drag and drop between columns to re-assign values and gain great visibility with custom swimlanes.
...
What standard fields to show?
You can select what stanndard standard fields to show on the card, namely
...
Cards color coding is JQL based. Just put a valid JQL, pick up the color from the palete palette and click Add.
Dependencies
Pick a dependecy dependency type you want to color and select a color from the palette to click Add.
...
GREY for statuses matching TO-DO status category
YELLOW for statuses matching IN-PROGRESS status category
GREEN for statuses matching DONE status category
But you can also change it. Just clikc click on any of the statuses and select a color from the paletepalette .