Skip to main content
System StatusContact Support
VersionOne Community

Summer 2020 Release Notes

Release Summary

Highlights Video

  • VersionOne:

    • Rebranding

    • Enforce Important Field Values at Close

    • Budgeting before Backlog

    • Portfolio Item Filter Changes

    • Performance Updates

Feature Breakdown

Team Edition Catalyst Edition Enterprise Edition Ultimate Edition Continuum ALM Connect
Rebranding      
Enforce Important Field Values At Close        
Budgeting before Backlog    
Portfolio Item Filter Changes        
Performance Updates    

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. August 8 August 8 August 15 August 15 N/A N/A

On-site

           
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 Thursday, July 30th, 2020 at Noon ET for a live review of the Summer 2020 release.

Click HERE to view a recording of the live webinar!

VersionOne

RebrandingRebranding.png

In April of this year VersionOne and Continuum were united with products from XebiaLabs and Arxan to form Digital.ai.  Both products have been rebranded to reflect the new organization.  This involved changes to the logo, the primary color, and to the main navigation bar. 

Enforce Important Field Values at CloseImportantFieldEnforceAtClose.png

Expanding on Important Fields, the Summer 2020 release introduces the ability to ensure values are provided at close for Important Fields defined in a Workspace . 

Enforcement is a Workspace configuration option.  When enabled Important Fields on assets in the Workspace are validated at close to ensure they contain a value.  To ensure fields values are correct the Quick Close option is disabled on assets in a Workspace where enforcement is enabled. 

Additionally, to help those responsible for auditing data, we added an Asset State filter option to the Product Backlog grid. This filter limits the results to assets in the specified State(s)  (Active and/or Closed).  The "Include Closed Items" filter remains, but is now implemented as an Asset State filter.

Budgeting before BacklogBudgetBySwag2.png

Budgeting capabilities have been enhanced to support budgeting based on the Portfolio Item SWAG, or ROM (rough order of magnitude), attribute.  All of the options available with Estimate, are now available with SWAG as well.  This means you can create capacity budgets, monetary budgets, or percentage budgets based on the Portfolio Item SWAG value.  And, Budgets can be based on Planning Levels or Strategic Themes. 

A a reminder, the Budgets capabilities in VersionOne allow the creation of multiple versions for any given criteria.   This enables the creation of Estimate or Swag based budgets for Annual, Half-year, Quarterly and Monthly. You can create multiple variations of draft budgets to examine different allocations.  Keep the one(s) you decide to go with and discard the rest.

In addition to adding support for SWAG based budgets, we also made the following changes to the Budgeting capabilities:

  • Updated the the Budget summary bars to clearly reflect how allocation, estimation (Points or SWAG), and progress align to the Budget.
  • Corrected a styling issue on the Delete Budget confirmation dialog and resolved a server error when deleting Budgets

Portfolio Tree FilteringPortfolioTreeFiltering.png

Portfolio Tree Filtering was expanded to include filtering options for the following scenarios: 

VersionOne enables Teams to have different levels of responsibility on Portfolio Items.  They can be the "Target Team", responsible for the overall Portfolio Item, or they can own work under Portfolio Items that are targeted to different Teams.  As the Product Owner on a team with both level of responsibility, I need the ability to see all Portfolio Items where we have commitments.  To support this scenario, we re-introduced the "Teams" filter on the Portfolio Tree, the Roadmap and the Portfolio Kanban. This filter returns Portfolio Items where the selected Team is the "Target Team" or where they are in the list of Teams owning work on the Portfolio Item (the Teams column on the Portfolio Tree)

As a Product Manager, or Product Owner, there are occasions when I need to see a single Portfolio Item and other occasions where I need to see child Portfolio Items of a given parent.  To support both scenarios, we changed the behavior of the "Portfolio Item" filter and added a "Portfolio Item Root" filter.  The "Portfolio Item" filter now returns the selected item.  The "Portfolio Item Root" filter returns all Portfolio Items under the selected Portfolio Item.  These results can be further refined with additional filters if necessary. 

Portfolio Items are organized hierarchically and intersect with the Planning Level hierarchy.  When viewing an unfiltered Portfolio Tree, the grid displays Portfolio Items in the selected Planning Level context that do not have a parent Portfolio Item in context.  We refer to these Portfolio Items as "Tracked Portfolio Items".  Because Planning Levels are also hierarchical, a Tracked Portfolio Items may or may not be in the selected Planning Level.  The default Portfolio Item filtering considers both hierarchies, but only returns Portfolio Items in the selected Planning Level context.  As a Product Manager, or Product Owner, I want to ignore the Portfolio Tree hierarchy and only filter Tracked Portfolio Items.  To support this scenario, we added a "Single Level" checkbox filter.  When this filter is applied, the Portfolio Item hierarchy is ignored and only Tracked Portfolio Items are considered.

Performance Updates

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

  • Grid Updates
    • Optimized grids queries when the "Status - Progression" column is visible
    • Backlog grids only refresh the affected row when the Planning Level is changed
  • Improved queries and rendering when Portfolio Items are grouped on the Roadmap Board view
  • Removed a memory leak in the heads-up chart in TeamRooms
  • Improved rendering of the Storyboard customize modal

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

Continuum

Enhancements

  • Worker install directories can be customized during install.
  • XL Release plugin supports Continuum dark theme.
  • A Flow plugin function has been added to retrieve rogue commits.
  • HTTP request detail has been enhanced for a pipeline step.

Fixes

  • Jira external functions not working properly.
  • Audit report removing zeros from time stamps.
  • Filters fixed on various pages.
  • TFS create branch canvas UI doesn't correctly list branches.
  • GitHub and TFS create branch canvas results in a crash of the UI service.
  • Pipeline Step Utility - HTTP function fails in multi-server setup with an external worker.
  • When upgrading Continuum the correct UI port was not being displayed.
  • Improved handling of Bitbucket Cloud repo names with a space in them.
  • Ability to set more than one default instance for a team.
  • Change sets created in V1 list unknown author always.

Other Enhancements and Updates

VersionOne

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

Enhancements

  • Added the ability to toggle Milestone visibility on Roadmaps.  The toggle applies to both Roadmap views, is Member specific, and the state is remembered between page views. 

  • The Request grid includes columns for "Portfolio Item Count" and the "Issue Count".  These columns are hidden by default but can be enabled in grid configuration.

    • "Portfolio Item Count" column indicates the number of Portfolio Items associated with the Request

    • "Issue Count" column indicates the number of Issues associated with the Request

  • The Issues grid includes columns for "Portfolio Item Count", "Request Count", and "Retrospective Count".  These columns are hidden by default but can be enabled in grid configuration.

    • "Portfolio Item Count" column indicates the number of Portfolio Items associated with the Issue

    • "Request Count" column indicates the number of Requests associated with the Issue

    • "Retrospective Count" column indicates the number of Retrospectives associated with the Issue

  • Numeric grid filters have an "Is Empty" and "Is Not Empty" options. This enables filtering grids to only include items that have, or do not have, a value in the selected numeric field.  For example, using the "Is Empty" filter on Estimate in the Backlog grid will result in Stories, Defects, and TestSets without an Estimate value being shown.

  • The Attachment relationship grid on asset detail pages contains information on who and when the Attachment was Created and Changed.  This information is also available on the Attachment Details page.

  • The "Group By" option on the Storyboard configuration page includes a "Reporting Category" checkbox when Status is selected.  This enables you to group the Storyboard by Reporting Category.  Remember, when Columned or Grouped by "Reporting Category", drag and drop is not supported.

  • Administration updates include:

    • The System Admin page contains an option to hide the System Information link on pages that do not require authentication (i.e. Login Page and Forgot Password Page).

    • The Custom Field table page contains a column indicating which List Type was used for Custom Drop Downs. 

  • CommitStream respects the Members Theme and Font Preferences in VersionOne

Fixed

  • Parent Planning Level can be reassigned before save when creating a child Planning Level from Release/PI Planning

  • Stories or Defects added inline from the Backlog Grid does not always save to the selected Planning Level

  • Exporting Members from the Member Grid on the Project Details does not export the Member's Project Role

  • Unexpected behavior when using drag and drop on Taskboard and Testboard to move Task or Test

  • Selection of Story/Task/Test Owner does not work using arrow keys

  • Portfolio Item cards on the Program Board lose their color when titles contain characters that interfere with wrapping

  • The Detail Estimate field is incorrectly labeled on the Close Dialog when marked as Important

  • When language preference is Chinese (Traditional) loading a TeamRoom page returns "Bad Request"

  • Teams without active work in status values inappropriately prompts for Team Process initialization

  • Cannot find unlisted Teams on Sprint Scheduling

  • Disabled check boxes were indistinguishable from active check boxes for required fields in Workspaces and for edit option in Customize Columns in grid customization

  • Cannot open TeamRooms from the Quick Search result list

  • Rank is a multi-select option on the Backlog Group grid

  • Project/Program Summary Report has an incorrect value for Open Issues

  • Progress Bars in My Dashboard no longer display the current date indicator.

  • Print and PDF buttons in My Dashboard are doubled

  • Story Velocity Reports erroneously have a Workitem selector filter

  • Cycle Time Display in Kanban TeamRoom does not consider the Member's "Include Weekends" preference

  • Cannot switch breakdown tabs on the PlanningRoom Scorecard

  • Corrected font issue in Scorecard Breakdown section

  • Team count summary metric on Scorecards is greater than the number Team listed in the Team breakdown grid

  • Play/Pause button on Scorecard Charts is not visible in all browsers

  • Cannot localize the first column of Breakdown grids on Scorecards

  • Incorrect asset icons alignment in Grids when some items contain the expand icon and others do not

  • Member avatar issues

  • Conversation mention issues

  • Members with usernames containing a backslash cannot access Analytics

  • Datamart ETL fails when certain list types are used for custom dropdown

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.