Skip to main content
System StatusContact Support Agility Community

Spring 2020 Release Notes

Release Summary

Highlights Video

  • VersionOne:

    • New Portfolio Tree

    • Important Fields

    • Edit After Close

    • Performance Updates

  • Continuum

    • XebiaLabs XL Release Plugin

    • Additional Team Level Plugin Support

Feature Breakdown

Team Edition Catalyst Edition Enterprise Edition Ultimate Edition Continuum ALM Connect
New Portfolio Tree        
Important Fields        
Edit After Close    
Performance Updates    
XebiaLabs XL Release Plugin          
Additional Team Level Plugin Support          

How to Upgrade


On-demand (auto-upgrade)

If your system is not in the auto-upgrade program, contact support to be added to the program or to schedule your upgrade. May 2 May 2 May 9 May 9 N/A N/A


Contact support for a new 2020 annual license for your on-site system.     Contact Us Contact Us Contact Us Contact Us
If you are not a current customer, and would like to learn more, visit our website and contact us to get started.  

Join us on Tuesday, May 5th, 2020 at Noon ET for a live review of the Spring 2020 release.

Click HERE to register!


New Portfolio TreeNew Portfolio Tree

The Portfolio Tree enables Product and Portfolio leaders to view and manage the Portfolio Backlog.  This backlog consists of Portfolio Items that deliver business value and break down into smaller Portfolio Items that can be implemented by Teams in a Release or Program Increment. 

While the look and feel is similar, the internals of the new Portfolio Tree have been improved and some behaviors have changed.  Major differences from the classic Portfolio Tree include only showing Portfolio Items by default, simplified filtering that respects the global context, and query updates that improve performance.  

All of the changes described here apply to the Portfolio Tree located in Portfolio Planning and the Portfolio Tree Panel in PlanningRooms.

In the new Portfolio Tree backlog items are hidden by default keeping Portfolio conversations focused on business value and how to deliver that value incrementally.  The new Tree includes a "Show Backlog Item" option to include Stories and Defects when that level of detail is necessary.   This change not only improves performance, it focuses conversation on what is most important at that time.  When "Show Backlog Items" is enabled, Stories, Defects, and TestSets are included under the appropriate parent Portfolio Item.

Other filter additions include support for filtering on Target Teams and filtering on Roll-Up Category values.  The Target Team filter limits results to Portfolio Items owned by the selected Team(s) and the Roll-Up Category filter limits results to Portfolio Items in the selected category.  Both of these filters were added to the Roadmap views and to the Portfolio Kanban.  Finally, the More Filter options were simplified to only include Portfolio Item attributes.  

In addition to new options, Portfolio Tree filtering now respects the global context selector (aka the Planning Level selector or the Product Tree Navigator).  This means that top level results only contain Portfolio Items in the selected context that meet the filter criteria.  As with the classic tree, filters do not apply to child items.  Therefore, when expanding Portfolio Items, child items outside the selected context are still visible.  This change aligns Portfolio Tree filter behavior with the behavior on other grids. 

The Portfolio Tree changes require an update to any saved Portfolio Tree views.  Any Member with Saved Views in the classic Portfolio Tree will see a Migrate option when opening My Views on the new Portfolio Tree.  Clicking this button migrates any existing views that do not contain Backlog Item filters and display a report on the results.  

These changes also impacted Expand All.  This option is no longer available because it significantly contributed to poor performance.  Expand All ignored the "Rows Per Page" configuration option which resulted in a large datasets being returned in bulk.  The new Portfolio Tree allows you to expand individual Portfolio Items one level at a time and the Collapse All option remains.  We have talked with several customers about the negative impact of this change and are considering ways to solve those problems without negatively impacting performance.

As of this release, the classic Portfolio Tree has been deprecated but it has not been removed.  If you need the classic Portfolio Tree, it can be enabled from VersionOne Preferences.  These settings are unique to each Member.

Finally, we would like to thank everyone who previewed the Portfolio Tree updates and provided feedback.

Important FieldsImportant Fields

As part of developing software many organizations need to capture meta-information about the work in order to satisfy downstream reporting requirements.  For example it is frequently necessary to categorize work to meet regulatory or financial requirements.  Such data needs can be quite diverse, with some groups having requirements that other groups do not. 

When meta-information is required it is important that the people doing the work remember to capture the data when it is known and that the value entered is accurate.   Requiring field entry presents a challenge when the information is not known or is not available at the time it is demanded by the system. 

Important Fields overcomes these challenges by making your data needs transparent without impeding forward progress.  This increased awareness improves understanding which in turn improves data quality.  People no longer "set it and forget it" because the system demanded a value. Rather, they can enter accurate information when that information is known.

Important Fields are configured in a Workspace for the desired Planning Level.  Once configured, these fields are highlighted when assets are Created, Edited, Viewed, and Closed using the close dialog. 

Edit After CloseEdit After Close

I admire people who consistently cross all the T's and dot all the I's.  I seem to always forget to set something and frequently don't realize it until later.  Therefore, I am very excited about our Edit After Close support. 

Edit After Close allows Members with edit permissions on an asset, to set values on blank, or empty, fields after the item has been closed.  You cannot change attribute values that were set before Close and once a value is set on a closed item, it cannot be changed again without first re-opening the item.   This change only applies to attributes, not relationships.

Performance Updates

There have been several performance updates to Scorecards and Roadmapping.  These changes were made available in point releases as they were completed.  Below is a recap of those changes. 

  • Scorecard improvements include dynamically loading data in the Breakdown grids and displaying the same chart on load and refresh.  We have also redefined "Active Portfolio Items" to mean Portfolio Items with Status Values in the "In Progress" roll-up category.  Finally all Scorecard queries were reviewed and optimized. 
  • Roadmap improvements includes changes to how Portfolio Items and Milestones are rendered, especially when grouped.  In the Timeline view, the Capacity chart, located at the bottom of the page, is no longer loaded by default.  The new chart is loaded and updated on demand.  It also includes a pin option for individuals who want this information automatically loaded.

We would like to thank everyone who partnered with us to identify and work through these issues.  We sincerely appreciate your feedback and patience.


XebiaLabs XL Release PluginCTM_XLR_Detail_Board_View.png

For enterprises utilizing the benefits of both XL Release and Continuum; a release in XL Release can now be triggered using a Continuum pipeline.   As changes occur in XL Release, the status of the release is updated in Continuum.  The current status can be viewed via the XL Release details page inside that particular step in the Continuum pipeline. As a result of the release in XL Release being a step in the Continuum pipeline, the flow metrics will include the duration of the release in XL Release as well.


Continued Team Level Plugin Supportimage (15).png

As an enterprise there may be times when plugins need to be restricted.  For example, an enterprise may need each team to use a specific Jenkins token.  With team level plugins when an instance of that plugin, Jenkins in this case, is created a team can be assigned. This will allow that team to only use that instance or available global plugin instances. 

New Plugins that Support Teams:

  • Bamboo
  • Travis CI
  • Kubernetes
  • Docker
  • Octopus
  • Parasoft
  • Teamforge
  • MS Teams
  • Slack

Other Enhancements and Updates


Select items included in this release that were completed since the last release.  Most, if not all, were available in previous point releases.


  • Enabled drag and drop from Teamroom Storyboard and List View into Estimably.

  • When a Member enters a PlanningRoom for the first time, the only selected panel is the first configured panel. Other configured panels are available, but are not selected.  Members may enable other panels and those choices are remembered

  • When a Member enters an Iteration TeamRoom for the first time, the only selected panel is the TaskBoard. Other configured panels are available, but are not selected.  Members may enable other panels and those choices are remembered.

  • When a Member enters a Kanban TeamRoom for the first time, the only selected panel is the StoryBoard. Other configured panels are available, but are not selected. Members may enable other panels and those choices are remembered.

  • Updated the graphic explaining the Dependency Visualization report

  • Increased the width of editable text fields on grids. 

  • Sidebar Enhancements

    • The Collaboration, Conversations, and Topic Sidebar options are now available via two icons: a Conversations Icon and a Collaboration icon.  The Conversations icon expands a tray containing Conversation related options - All Conversations, TeamRoom Conversations, PlanningRoom Conversations, Spaces, and Followed Members.  The Collaboration icon expands a tray containing Communities and Topics.

    • The Recycle Bin icon was moved to the Search panel. 

  • Webhook notifications are published when Attachments are created, updated, or removed


  • Tags are removed from the Tag Administration grid when all associated asset are closed

  • Cycle Time Reports does not honor the "Show Weekends" preference

  • Card threshold count does not honor the "Show Weekends" preference

  • Exception is thrown in Webhooks when a Member is deleted

  • Incorrect cursor in text fields

  • Issue grid incorrectly filters on Blocked Issue count

  • Timeline Roadmap navigation controls are finicky when they are in the included under the "more options" icon.

  • The Show/Hide label on Detail Pages cannot be localized on the Terminology page.

    • Note: The new localization values are Label'Details'Empty Fields'Show and Label'Details'Empty Fields'Hide. These can be added in the "Other Localization" section on the Terminology page.

  • Corrected Description display issue when viewing Communities and Topics
  • Status value options are incorrect for Teams with a process when a Story is Generated from a Request

  • The Team filter on the Issues page only includes Teams that own work items

  • Lookups that rely on search (i.e. Portfolio Item Filter on Grids) do not find matching items

  • Expanding a Portfolio Item, on the Roadmap Timeline, without permission to child Portfolio Items results in blank screen

  • Labels on Budget charts are no longer visible

  • Unable to load grids on the Ideas pages

  • Close panel in TeamRooms doesn't update when there are a lot of closed items
  • Description field in Grids are no longer formatted correctly

  • Cannot drag items from the Storyboard to the Backlog in TeamRooms

  • Miscellaneous Icon Updates




  • Newly created teams require a user to log out and log back in.
  • Clicking on an automated task of a pipeline instance does not show detail. 
  • Gitlab submissions are not able to call back to the server.


System Requirements Changes

There are no System Requirement Changes in this release

Point Releases

For a complete listing of point releases, see Point Release Notes by Product.