Skip to main content
System StatusContact Support
VersionOne Community

Delivery at a Glance

This feature is available in Enterprise and Ultimate editions.



Delivery at a Glance provides clear visibility of the evolution of your product from development all the way to your customer’s hands, right from within VersionOne Lifecycle. From product inception to delivery, you can easily identify work items and commits contained in VersionOne Continuum™ packages and watch work items increase in maturity as they flow across the value stream.

A valid Continuum instance is required in order to use Delivery at a Glance. Find out more at the Continuum Community Page.

Accessing Delivery at a Glance

Delivery at a Glance is located in the Release Planning menu item on the navigation bar.

Delivery at a Glance Menu Location

How it Works

Delivery at a Glance provides shows a visual representation of each of your delivery phases and their contents, as follows:

  • Phases are each one of the steps in your delivery pipeline (e.g., development, staging, production).

  • Packages are the main elements presented in each delivery phase. Packages contain work items, which in turn contain, one or more commits. Packages contain a reference to the Continuum package promotion that triggered its creation.

  • Work items are the contents that populate each package. These are primary work items only (stories, defects, and testsets). 

  • Commits are the units of change associated with each work item on the board. These come from your version control system, which is monitored by Continuum. The board is driven purely by the commits that are coming from your version control system into Continuum and their relationships to work items and packages in Continuum.

Interpreting the Delivery at a Glance Board

The board is comprised of the following elements:


A phase represents a particular location in your delivery pipeline. The heading displays the phase name ("Test" in this example) and the total number of unique work items contained in this phase. If the same workitem is contained in two separate packages in the same phase, this total will only count the work item once.


A package is the container of work items presented in each phase. It is comprised of worki tems and commits. Its heading contains its name, last updated date & time, as well as total number of work items.

Undeliverable Work Item

Undeliverable Workitem

The light shaded square represents an "undeliverable" work item. This means the work item's status belongs to a "not started" or "in progress" reporting category.

Undeliverable Work Item with Trailing Commits

Trailing Commits

The light shaded square split with a diagonal line represents an "undeliverable" work item which contains trailing commits. This means there are additional commits for this work item in a package located in an earlier phase that are not contained in the package you are currently viewing. Effectively all the work that has been committed against this item is not in the current package and thus is not deliverable.

Deliverable Work Item

Deliverable Workitem

The dark shaded square represents a "deliverable" work item. This means the work item's status belongs to a "completed" reporting category and all the commits for the work item are found in this phase/package. This means no newer commits are in any of the preceding phases and thus the work item can be delivered.

Rogue Commits

Rogue Commits

The orange box located at the top right of a package represents the number of rogue commits contained in the package. These are commits that were not associated with any particular work item and thus are rogue. This generally happens when a commit is not tagged with the work item ID the work was intended for (ie. S-12345) or because the story branch where the commit is located does not contain the correct work item ID.

Toggling Between Available Views

The Delivery at a Glance board offers 3 different views (controlled from the top toolbar)


  • Packaged 

Shows workitems within the boundary of their respective package in the given phase

  • Unpackaged: Shows the total number of unique workitems for the given phase; note that if the same workitem is participating in multiple packages for the given phase, it will only show once in the unpackaged view.

  • View by Portfolio Item: Shows the distribution of workitems across your delivery workflow by Portfolio Item. This mode also offers the number of workitems that have are "done vs. delivered", allowing you to identify work that has been completed but not yet shipped. Additonally, you may drill-down to see children Portfolio Items by clicking on the plus "+" sign to the left of the Portfolio Item name.

When "View by Portfolio Item" toggle is enabled, the following controls become available:

  • "Portfolio Item Type" filter: Use this filter to view only Portfolio Items of the type you select, for example "Initiative" or "Feature".
  • "Portfolio Item Owner" filter: Use this filter to view only Portfolio Items owned by a particular Lifecycle member.
  • "Percent" precision toggle: Use this toggle to view percentages for the distribution of work across portfolio items as well as % "Done" and % "Delivered".
  • "Count" precision toggle: Use this toggle to view workitem count for a particular phase on the portfolio item as well total workitems "Done" and total workitems "Delivered".

Closing or Deleting Packages

The Delivery at a Glance board allows you to close or delete packages whenever necessary.

  • Closing Packages: Closing a package is appropriate when all the work associated with the package has been completed and there is no further value displaying this package in the board. A common example is when a package has been in the final phase for an extended period of time. To close the desired package simply click on the package title, click the "Edit" menu and select "Close".

  • Deleting Packages: Deleting a package is appropriate when the package was created or promoted in error. A common example is when a package was labeled incorrectly in Continuun or was given the wrong version. To delete the desired package simply click on the package title, click the "Edit" menu and select "Delete".

How to Configure Your Continuum Instance in Lifecycle

To configure Delivery at a Glance, your Admin Privileges role must be set to System Administrator.

  1. From the Admin menu, select DevOps > Continuum

  2. Enter your Continuum Instance URL, your Continuum API Access Token, and then click Save. This validates your Continuum instance and saves the configuration. Note that your Lifecycle instance must be able to reach your Continuum instance over the internet.

Your Lifecycle instance must also be properly configured in Continuum in order for the data to flow properly. See VersionOne Setup in the Continuum docs portal.

How to Map Delivery Phases in Lifecycle

  1. From the Admin menu, click the List Types tab, and then click on the Global tab.

  2. In the Phase grid (at the top of the page), add your delivery phases in sequential order, starting from the earliest phase. This should mirror the phases you previously setup in your Continuum progression configuration.

  3. From the Admin menu, click Display Fields, and then click Project Workspace Assets to enable the newly created phases.

  4. Click on Phase group, and then select the check boxes next to each phase under Display.

Phase Configuration in Lifecycle

If you are making use of the "Project Workspaces" feature, you will need to do this step for each of the projects which have a dedicate workspace.

Not a Continuum User?

To learn more see:

  • In the Summer 2016 Point Release #1 - Build release, these features were added: support for Continuum Package updates, the ability to associate rogue commit with a work item, and bundles that contain only rogue commits display. Older versions of the application do not contain these features.
  • Summer 2016 Point Release #3 - Build, these features were added: unbundled work items, a legend was added to the top right corner, the ability to remove/disable continuum instance information, the ability to configure phases without first validating Continuum instance information, and "Bundles" were renamed to "Packages". Older versions of the application do not contain these features.
  • In the Summer 2016 Point Release #4 - Build release, custom label support for packages and rogue commits that exist on next phase do not show up on prior phase were added. Older versions of the application do not contain these features.
  • In the Summer 2016 Point Release #7 - Build release, the Board views are renamed to "packaged" and "un-packaged". Older versions of the application does not reflect this change.
  • Was this article helpful?