Skip to main content
System StatusContact Support Agility Community

Winter 2013 Release Notes

New Visualizations      
Epic Relationships    
Epic Cross-Project Visability    
Streamlined Epic Breakdown    
Threaded Conversations
OpsHub Integrations
Other Platform Updates
API Changes        
System Requirements Changes
On-Demand Training


Contact your account manager* to upgrade your On-Demand system.

Contact your account manager* to obtain a new 2013 Release annual license for your On-Site system.

Ultimate Edition
Enterprise Edition

 *Lost your account manager’s contact info? Email us at


Release Summary Video


Sit back and watch as we walk through the major features of this release. The Release Summary video includes segments on:

  • New Visualizations
  • Epic Updates
  • Threaded Conversations
  • OpsHub Integrations


VersionOne_Release_Notes_-_Winter_'13_Dependencies.pngNew Visualizations


The new project dependency visualization provides insight into the delivery sequence for open dependencies in the selected project or program. In addition to active dependency relationships, the project dependency visualization indicates blocking issues, schedule conflicts (aka broken dependencies), and circular dependencies on stories with dependencies. For scheduling conflicts there is information provided in the tool-tip to better understand the impact of the conflict. The project dependency visualization is available in the in-line reporting links on the following pages: Backlog, Release Scheduling, and Iteration Scheduling.


Two new visualizations were added for Themes. First, a tree visualization can be used to explore the complete hierarchy for a Theme, including the Stories, Defects, and TestSets that comprise the selected theme. Second, a contextual visualization was added to increase understanding of Theme relationships. This context includes the Goals being satisfied by the Request; the parent Theme and all child Themes; and finally all Stories, Defects, and TestSets that comprise the Theme. Since there are multiple visualizations for Themes, the Visualization icon on the hover will take users to the last visualization viewed and the Visualization menu item has a sub menu.


VersionOne_Release_Notes_-_Winter_'13_Epics.pngEpics received a new contextual visualization that provides increased relationship understanding of an epic. This context includes the Request, and/or Ideas, used to originate the Epic, the Epic's parent and all immediate children, all Stories, Defects, or TestSets directly related to the Epic, and finally any Issues that are blocking the Epic's progress. Since there are multiple visualizations for Epics, the Visualization icon on the hover will take users to the last visualization viewed and the Visualization menu item now has a sub menu.


There are also new contextual visualizations for Goals, Issues, and Requests.

  • Goals - the context includes Themes and Workitems that satisfy the Goal.
  • Request - the context includes Epics, Stories, Defects, TestSets, and Issues that were generated from the Request.
  • Issues - the context gives us a complete picture of all Stories, Defects, TestSets, and Epics blocked by the issue along with the Request that was used to generate the Issue.

The contextual visualization for Defects was enhanced to provide a complete picture of all Stories, Defects, and TestSets that are broken by the Defect.

The contextual visualization for Stories, Defects, and TestSets were enhanced to include Task, Test, and Request relationships. Additionally, the existing Epic and Theme relationships are collapsed by default to improve readability. These relationships can be expanded if necessary to show the full hierarchy.

All contextual visualizations received the following enhancements:

  • Relationships are in consistent locations across all items whenever possible.
  • The multi-relationships hubs are collapsed by default when a multi-relationship contains more than 3 items. Clicking on the hub will expand all children.
  • The multi-relationship hubs are no longer animated.
  • Cards are restricted to the visible area.
  • A "View Options" menu was added to the diagram. This menu allows members to control what relationships are visible. These options persist between session and are unique to each visualization and each user.

New Epic Relationships


Use requests to generate new epics, allowing you to establish a link back to the original input from one or more sources. Requests can be used to create new epics, or you can manually link one or more requests to an existing epic. Requests linked to a higher level epic will be visible to all child epics, stories and defects so team members working on this items can reference details from the request(s) that helped to drive them.

Ideas (Ultimate edition only)

Link ideas directly to epics so that external input collected in your Ideas system is visible from the epic and its children. Ideas Forum Administrators are able to establish the links, which are then visible to all team members. Ideas linked to a higher level epic will be visible to all child epics and stories.

Epic Cross-Project Visibility

You now get a full functional view of any epic in the epic tree, even if details are being delivered by another organization. The epic tree query was updated to include all children of epics in the selected scope, regardless of where those children sit in the project hierarchy. This helps matrixed organization and complex project setups to see all the detail every time. This allows full visibility to, for example, an epic to owned by a development team with a story that being delivered by a centralized security team that sits in another organization. The security team's story is always visible in the epic tree when looking at the parent epic, so you never miss an important detail.

  • Along with this enhanced visibility come a couple of other changes:
  • Two new columns have been created to view 'Scoped' epic estimate and progress bar rollups. These new columns are available when customizing the epic tree view and show totals that come solely from child backlog in the currently selected project, allowing you do exclude backlog that will be delivered by other projects or organizations.
  • The Delivery Projects section of the Epic Dashboard view (Ultimate Edition Only) has been updated to include project-level rollup numbers that are specific to the selected epic. Previously, only the values shown by default in the view were specific to the selected epic. Now, you can customize the view to show any numeric column and see epic-specific values.

Streamlined Breakdown

VersionOne_Release_Notes_-_Winter_'13_Streamline_Breakdown.pngYou can now decompose your epics easier and with fewer clicks. Breakdown features that previously existed in a separate Epic Breakdown popup page have been moved directly to the Epic Tree page and, in a more limited sense, to the Epic Details view. These changes have allowed for the removal of the now-redundant Epic Breakdown popup view. The Epic Tree alone can now be used to break down and manage your epic hierarchy, regardless of where child items sit in your project tree. The epic details page, which can be accessed from anywhere you view an epic, has been updated to allow you to decompose the epic into a single level of child epics and/or stories and to assign any existing backlog (stories, defects or test sets) to the selected epic.

Threaded Conversations

See entire threaded conversations related to assets inline on the details view of any asset. This means that all replies in a conversation thread will be visible on the details view even if the reply doesn't explicitly mention the asset. Expandable conversation threads show mention and participant summaries when collapsed. All primary activities have been redesigned inline to prevent you from losing context of an asset's details and without overlapping any other information in the view. These activities include paging through older conversations, starting a conversation and replying to conversations.

OpsHub Integrations

VersionOne is proud to announce our new partnership with OpsHub. OpsHub Integration Manager is an ALM integration platform. With connectors for over 2 dozen ALM products, OpsHub bring about a dozen new integration targets to VersionOne. OpsHub synchronizes stories, defects, tests, and tasks to and from VersionOne, which brings new options for some existing integrations. OpsHub pricing varies by users, number of end-points, and assets synchronized; however, for common forms of integration OpsHub will be more affordable than custom development and without the wait.

  • Accept 360
  • Accompa
  • Chilli Project
  • FogBugz
  • IBM Rational DOORS
  • IBM Rational RequisitePro
  • IBM Rational Team Concert
  • Redmine
  • Seapine Test Track
  • Serena Business Mashups
  • SmartBear Software Planner
  • Trac

Platform Updates


API Changes


System Requirements Changes

Added Support for:

  • Windows Server 2012
  • IE10
  • Windows8

Note: As of this release, the system requirements will no longer include specific version numbers for rapid release browsers (Firefox and Chrome) and Safari. Testing will continue to be conducted using the latest available production version of each browser prior to the release. Version numbers for supported Internet Explorer browsers will continue to be specified given the significant behavioral differences between IE browser versions

On-Demand Training

VersionOne’s new on-demand training is now available to allow your users to participate in structured online training according to their schedule, at their own pace. Get more information.


  • The Cumulative Flow diagram on the Standup Dashbaord has been updated to prevent a sudden drop to zero for future dates. The cumulative flow display now ends by default on the current date for in-progress iterations, or on the last day of a past iteration.
  • The Team filter dropdown on Analytic Dashboards uses a more performant query to retrieve data.

In addition, the following additions were rolled out in point releases since the last quarterly release:

  • Improved error handling on start-up.
  • Added the ability for Project Leads (or above) to delete TeamRooms.