Contents:
What is release view
Release view provides a compact view for teams to oversee an ongoing release from the inside with all its details. This view enables to quickly find user stories belonging to a particular release and get instantly an up-to-date status about the development. To make this experience even better cards are listed on a dedicated kanban style interface.
Release view is deeply connected to the story map itself and works with it in real-time. Any modification is made on release view it will be also implemented on the story map. This means e.g. to create a new story card on release view or change the status of a card and that will be also synced with the story map.
The purpose of release view
Release view amis to enhance productivity and team experience by supporting the following activities:
to gain quick overview of an ongoing release in a simple yet powerful way
to involve dev teams’ and enhance their efficiency on a dedicated interface
to utilize the kanban board in daily stand-ups and access the right information
How to access release view
There are two ways to access release view depending on the story map interface you are using:
On the NextGen story map interface
open the story map
select “Tracking”
choose the release you want to see in details
On the Classic story map interface
open the story map
select “Tracking”
choose the release you want to see in details
What actions are available on release view
Edit release details
The team can access details about the release and have discussions over the release view interface. To support the team with more information click on “Release details” to access the entire overview of the release. To edit details about the release simply click on the release description to modify its content.
💡 Tip - Learn more about Release management.
Set start and end date of the release
You can set or modify the start and end dates of a release even on the release view by selecting the date and set new one in the calendar. Release dates can also be modified in “Release details“ window opening it on the story map or on the release view interface.
Parent cards filtering
When the team opens a release in “Release view” they can drive the conversation using the product backbone (parents cards). This represent the 1st and 2nd level cards on the release view to provide context for the team. There are two useful scenarios here:
Selecting a parent card or even multiple ones to quickly list the related user stories:
Displaying parent cards related to a user story card
Column activities
In case the releases are used as iterations and when one iteration is ending there is a possibility to move all remaining cards from a column to another release or modify card’s statuses with a simple action.
Available column activities:
Move cards to another status
Move cards to another release
Create new story cards
When the team is discussing details about the ongoing release on release view they may face a situation when they realize they forget something and they need to add a new card to the release. To resolve this case, you can instantly add a new story card to the release directly on from release view interface.
To add a new card simply click on the add new card button with the “+” sign.
Please note that
the new card will be added to the release you are looking at on the release view.
the new card will be created with the same status you created a card in
actions are real-time between release view and the story map
the new card will also appear on the story map
When you created a new card on the release view interface, they will be also visible instantly on the story map following these conditions:
new cards will be placed under “Unordered user stories” column in the first column of the story map
new cards will be created in the associated release to the release view where the card was created
new cards will also hold the same status information where the card was created on release view
Now that you have new cards also on the story map, you can organize them within the release and move them under the right parent cards and priority order within the column. You can also move it into another release if the card was mistakenly created in a wrong release.
Once al cards has been moved from “Unordered user stories” column, you can simply delete this placeholder if you wish to do so.
Multiple card selection
Multiple cards can be selected to perform bulk operation to change the selected cards’ properties. This allows you to add/remove annotations, personas, change cards color or status, and even assign a team member to multiple cards all in one action.
💡 Tip - Learn more about Multiple card actions.
Filter relevant cards
There is a dedicated filter option that helps to find instantly cards with relevant content at any time. The filter provides options that makes conversations easy and drive discussions by displaying the right content of the board.
Here are a few example you can so among other alternatives as well:
filter by the creation or updates
filter by colors
filter by personas
filter by states
filter by assignees
To access the filter menu open the “Filter tab” on release view and select the right option for your action. The filter instantly returns with the right information and it indicates the how many cards are matching to the selected filter requirements. There is an option to click on select cards to customize further the result.
In case you click on “Select cards” option for your filter result page, you can enable multiple card actions on the selected cards to perform. This will allow to change all selected card’s properties in one go.
💡 Tip - Learn more about Multiple card actions.
The following options are available:
Add / remove annotation
Change card color
Move to another column
Change status
Add assignee
Delete selected cards
If you do not proceed with the “Select card” option on the result page of the filter, then the result will be displayed on your board and showing only those cards that are matching with your filter criteria.