Skip to main content
System StatusContact Support
VersionOne Community

Winter 2012 Release Notes

  • Ultimate
  • Enterprise
  • Team
 
Agile Portfolio Management      
Epics Updates    
Clarity Integration    
Data Mart Updates    
Analytics Updates      
Integration Updates  
API Changes  
System Requirements Changes  
Miscellaneous  

 

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 Info@VersionOne.com.

 

Note: Data Model Changes
This release contains a number of data changes that will impact your usage of Epics and, potentially the API and reporting. Please read the below release notes carefully prior to upgrading for details on the changes.

Agile Portfolio Management

Winter_'12_Agile_Portfolio_Management.pngNew Epicboards and Dashboards view bring Agile and Lean principles to higher levels in your organization. Use these principles to gain visibility of plans and progress not just at the project team level, but also for programs and entire portfolios. Each level of your organization can customize their flow to track their epics through an appropriate process. Executives or Steering committees can guide the organization's strategic direction by defining, prioritizing and approving high level business initiatives. Programs teams then decompose their relative portion of those initiatives to identify the work they need to deliver for each initiative. Further decomposition by project teams identifies the stories for their respective backlog. Focused visibility, context and tracking exist at each level to keep the project team work in synch with strategic plans, which those at the higher level are kept aware of lower level progress.

Agile Portfolio management is available in Ultimate Edition through the features below.

Epicboard

Winter_'12_Epicboard.pngEach project has its own Epicboard to visualize and track its epics as they move through the delivery process. Through the use of project workspaces, each project has the capability to define an appropriate flow on its board. Through the hierarchical nature of epics, groups at different levels of the organization can plan and track epics at varying levels of detail. Those at the highest levels of planning will be able to see and track the big-picture epics. Those at the project team level will be able to see and track the components for which they are responsible.

The Epicboard works in much the same way as the Storyboard. Epic cards are physically moved across the board to reflect advancement through the process and/or moved up or down within a column to change the relative ranking of the items. Board Customization options allow for the definition of Policies, WIP Limits and Swimlanes. Through the cards, team members can Edit the epic, use Breakdown to further decompose it, view the Epic Dashboard (see below), or reflect a Blocked Epic. Board filtering provides a method to narrow in on a subset of the tracking epics (the most coarse-grained epics in the selected project which naturally display on a given Epicboard).

Epic Dashboard

Winter_'12_Epic_Dashboard.pngThe Epic Dashboard is a new tab on the Epic Details view that provides a overall status of the epic and a breakdown of its details along both functional and project dimensions. The Epic Dashboard is the first stop to answer questions about epic status, identify any red flags for delivery, gain a deeper understanding of which components of the epic are complete and understand which project teams are contributing to the epic. The Epic Dashboard can be used as a launching pad to dig further still into the details to resolve any questions or issues.

Use the action menu on any epic card on an Epicboard to jump directly to the Epic Dashboard.

 

Epic Updates

Several enhancements have been made to Epics to provide greater functionality and flexibility.

Epic Tree

You can now re-rank epics in the tree using simple drag-and-drop capabilities. This capability is available in both the Epic Tree page and the Epic Breakdown view.

  • Drag onto an item reassigns the parent.
  • Drag above or below an item ranks the item being dragged in that spot.
  • Drag above or below an item under a different parent epic to both reassign and rank it.
  • Re-rank is possible only when sorted by rank, though the drag to reassign function works regardless of sort order.

Epics are 1st Class Assets

Epics have risen in stature. No longer a sub-type of stories, epics are now their own 1st Class Asset. This change resulted in a number of updates to both the Datamart and the platform / API - see the appropriate sections below for more details.

This creates a number of benefits and general impacts:

  • Epics now have their own unique Fields. You'll see values such as an ID with an E-xxxx format, a new Swag value for high level estimates and a Status field that is distinct from the story's Status.
  • Custom fields can now be created uniquely for epics.
  • Flexibility in project workspaces with the ability to show/hide these epic fields and control list value displays independently of stories.
  • Epics are their own asset in RESTful API queries (https://server/VersionOne/rest-1.v1/Data/Epic)
  • Epics have their own tab on the .xls Import Template.
  • Any references that point directly to old-style epics (e.g. an old url to an Epic Details view) will reference the newly-created epic after an upgrade.

Epics in your old system will be automatically converted to the new 1st Class epics during your system's upgrade.

  • Many fields transfer over directly to the upgraded epic: e.g. Title, Description, Reference, Source.
  • Some new fields exist on epics. These fields will be empty after the upgrade.
  • The following list type (i.e. dropdown) fields have been split off from stories for the new epics. All data is transferred as part of the upgrade, so there is no visible change in the values for your epics:
    • Status
    • Type
    • Priority
  • Some relationships that applied to Stories do not apply to Epics, including:
    • Team
    • Theme (or Feature Group)
    • Customer
    • Request
    • Issue - (resolved by relationship only; Blocking Issues are supported)
    • Goal
  • Tests on old-style epics served as a template during breakdown rather than trackable tests. These tests are not converted to the new epics.
  • Custom fields on the story asset are not recreated on the upgraded epic. If custom field data was used on old epics and needs to be transferred to the upgraded epics, please contact support to assist.

Breakdown

The drag-and-drop updates that allow both ranking and reassignment are available on the Breakdown Epic view.

In addition, the Breakdown actions have been updated to reflect the new 1st Class status of epics, which drives some changes.

  • Relationships are not copied down to child epics or stories during the breakdown process, which includes:
    • Links, Attachments and Conversations
    • Tests on epics are for trackable testing and are not copied
  • The following actions applied to epics as a sub-type of story, so have been removed. Note that the Breakdown function can be used in place of these actions:
    • Convert Story to Epic (use Breakdown Story action instead)
    • Convert Epic to Story (use Breakdown Epic action instead)

Clarity Integration

Winter_'12_Clarity_Integration.pngA new PPM integration is now available for CA Clarity. The integration allows you to load projects into VersionOne using your CA Clarity PPM Demand Management process and keep project summary data up-to-date with updates from your project teams working within VersionOne.

Data Mart

Epic Updates

The VersionOne Data Mart database and ETL were enhanced to support the changes made to Epics in the VersionOne application.

  • The following columns were added to the Epic Dimension (Dim.Epic):
    • EpicRisk
    • EpicSwag
    • EpicValue
  • The following columns were removed from Epic Dimension:
    • EpicAssetSubState
    • EpicBuild
    • EpicCustomerName
    • EpicIterationName
    • EpicPlannedEstimate
    • EpicRiskName
    • EpicSplitFromDisplayID
    • EpicSplitFromName
    • EpicTeamName
    • EpicThemeName

Setup Changes

The Data Mart Setup program was modified to drop the existing data mart database and create a new one.

Warning Due to the extent of the Data Mart changes, the Setup utility will drop your existing Data Mart database and create a new one. After running Setup you need to run the Data Mart ETL (VersionOne.DatamartLoader.exe) with the Full mode option:
VersionOne.DatamartLoader.exe /Mode:Full
This will result in a full load of the Data Mart database and will take longer than the typical ETL run.
If your database was not created by SetUp (you run setup with the UseExistingUserOption), then you will need to manually drop the existing database and create a new Data Mart database.

Ultimate Edition Customers:

As a result of the changes to Custom Reporting, the Data Mart ETL now loads Users and Custom Fields from VersionOne into the Custom Reporting meta-data database. The ETL no longer handles other meta-data changes. As a result, you need to install, or upgrade, Data Mart and Analytics before running the ETL.

Analytics

Backlog Matrix

Winter_'12_Backlog_Matrix.pngThe Backlog Matrix enables the comparison of complex data at a glance. It accomplishes this by slicing data by four dimensions. The end user selects two dimensions for a chart, and then two more dimensions for the matrix. They can also filter the data being considered and change the charts aggregation method. Clicking on any chart will zoom-in on that image. From the larger image, users can view the data in a table by clicking on the Details button. As the name implies, only backlog item data (Stories, Defects, and TestSets) is presented in this report. The report is located under Analytic Grids.
Custom Reporting Improvements

 

Custom Reporting

Winter_'12_Custom_Reporting_Improvements.pngThe Custom Reporting component of Analytics received an upgrade in style and behavior. Enhancements include:

  • The separation of data retrieval from data presentation is more obvious in the report creation wizard.
  • When selecting data, there is addition information about tables and columns.
  • The table names were changed to better describe the data they contain.
  • A Preview options allow report creators to see data before using it in a report.
  • Changes to the reporting meta-data reduce the possibility of joining incompatible tables.
  • Creating Calculated Columns and Statistical Columns is easier.
  • Report Templates make getting started easier.
  • The Chart Selection Gallery makes selecting a chart easier.
  • Additional Chart, including multi-layer charts that supports two data series on the same chart.
  • Drag and Drop support for moving report elements on a page.
  • New "Quick Report" queries have data columns preselected.
  • VersionOne Members with a Default Role of System Admin can manage report definitions under Shared Reports.

The Custom Reporting meta data was also modified to support the changes made to Epics in the core VersionOne application.

  • The following attributes were added to Epic.
    • Risk Scale
    • Swag
    • Value Scale
  • The following attributes were removed from Epic.
    • Build
    • Customer Name
    • Iteration Name
    • Planned Estimate
    • Risk
    • Epic Split From Display Id
    • Epic Split From Name
    • Team Name
    • Theme Name

Setup Changes

As a result of the Custom Reporting UI changes, the Setup program is now responsible for loading Custom Reporting meta-data and sample reports.

Warning As a result of this change, Analytics Setup must be completed before running the Data Mart ETL.

Other Enhancements

  • Project tree control in Custom Reports is sized appropriately for the data.
  • The Velocity Trend sample report in Custom Reporting matches the Velocity Trend report in VersionOne.
  • VersionOne user added between ETL runs see a user friendly error message.
  • Performance improvements on Analytic Grids.

API Changes

The items mentioned below represent a summary of the changes. For additional details on Core API and SDK changes, please see Core API Changes for 12.0.

Core API Updates

This major release includes a number of Core API changes. These changes are the result of the following activities:

  • Epics as first-class citizens - Prior to this release, Epics were Stories with a specific Substate. If you were using the API to report or manipulate Epics, you will need to recode these queries. Fortunately, as first-class assets, new queries will be simpler to write and maintain
  • Consolidation of Expression relationships - Prior to this release, Expressions could mention Members or any subtype of BaseAsset so that Conversations could be related to other AssetTypes. Since Members are a subtype of BaseAsset, there were cases where the wrong relationship was applied to Members. The 2 relationships have been consolidated into one relationship with BaseAsset. This should not have an impact on existing API queries.
  • Clean-up of attributes and operations - Prior to this release, there were some exposed attributes and operations that had no valid use. These were removed to help avoid confusion and unclutter the metadata.
  • Advanced Search with AssetState - New attributes help expose options for searching on asset state in advanced search.

.NET SDK Updates

  • Changed: Framework version to .NET 4.0
  • Changed: Object Model Epics from old style (substate of Story) to new style (first-class meta element)
  • Changed: Object Model Conversations to reflect BaseAsset/Member change in core API
  • Changed: Clean up of unused/nonsense attributes and operations (per core API clean up)

Java SDK Updates

  • Changed: Object Model Epics from old style (substate of Story) to new style (first-class meta element)
  • Changed: Object Model Conversations to reflect BaseAsset/Member change in core API
  • Changed: Clean up of unused/nonsense attributes and operations (per core API clean up)

Integration Updates

Bugzilla Integration

  • Fixed: Reopen scenario so reopening Bugzilla Issues creates new VersionOne workitems with link to previous item
  • Fixed: Line-endings for Perl scripts for Linux
  • Fixed: Problem with selecting custom VersionOne field for reference

ClearQuest Integration

  • Fixed: Reopen scenario so reopening ClearQuest Defects creates new VersionOne workitems with link to previous item
  • Fixed: Problem with selecting custom VersionOne field for reference

ElectricCommander Integration

  • Added: Support for ElectricCommander 4.0

Hudson Integration

  • Added: Support for Hudson 2.2
  • Fixed: Incorrect ChangeSet time for Git and Svn

JIRA Integration

  • Fixed: Reopen scenario so reopening JIRA Issues creates new VersionOne workitems with link to previous item
  • Fixed: Problem with selecting custom VersionOne field for reference
  • Fixed: Exceptions thrown when there are no project mappings

Perforce Version Control Integration

  • Added: Support for Perforce 2011.1

Quality Center Integration

  • Fixed: reopen scenario so reopening Quality Center Defects creates new VersionOne workitems with link to previous item
  • Fixed: problem with selecting custom VersionOne field for reference

IntelliJ Integration

  • Added: Support for IntelliJ 11

Subversion Version Control Integration

  • Added: Support for Subversion 1.7

Visual Studio 2010 Integration

  • Fixed: Honor effort tracking settings from server
  • Fixed: Refresh data after changing VersionOne instance
  • Fixed: Closing and quick closing require manual data refresh
  • Fixed: ToDo not updating after edit
  • Fixed: Owner editor combobox with multi-select

System Requirements Changes

  • As described in the prior release, with this release support has been dropped for IE7. Please ensure your users are able to upgrade to IE8 or IE9 or use one of the other supported browsers prior to upgrading your system.
  • Microsoft .Net 4.0 is now the required server Framework level.
  • Updated versions for the following browsers:
    • Firefox 10
    • Chrome 16
  • Removed the specific list of RSS Readers for RSS Notifications.

Miscellaneous

  • A new import spreadsheet template exists that includes Epics as a separate import tab.
  • Cumulative Flow graphs have been changed to be area charts.
  • Was this article helpful?