Skip to main content
System StatusContact Support
VersionOne Community

Summer 2012 Release Notes

Customizable Storyboard Cards  
Printable Cards
Defects and Test Sets in Epics    
Epic Bubble Chart      
Analytics Updates      
Data Mart Updates
Platform 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.

 

Release Summary Video

Summer_'12_Video_Image.pngSit back and watch as we walk through the major features of this release. The Release Summary video includes segments on:

  • Customizing storyboard cards
  • Printing cards
  • Associating defects and test sets with epics
  • Analyzing epics with the new Epic Bubble Chart
  • Analyzing epics with new Analytics reporting capabilities

summer_'12_Customizable_Storyboard.pngCustomizable Storyboard Cards

Allow your teams to customize their view of cards on the Storyboard. Through the board configuration, cards can be configured to show information appropriate for the team. A project team can elect to show member avatars, progress bars or custom fields directly on the cards. In addition, a new optional display location has been added as a card tab to allow more data to be displayed. Hovers on the field data help occasional viewers understand what fields they are seeing on the cards.

Printable Cards

summer_'12_Printable_Cards.pngPrint cards directly from the application to create physical boards, use for estimation games or other physical organizing activities. Use filters on the grid to narrow the selection of cards and then use the grid's wrench menu to print the cards out. All cards come with a QR code that allows direct electronic access back to the details view of the item using a standard mobile QR code reader on your smartphone or tablet. Cards print 4-up on a 8.5in x 11in sheet, providing a standard sizing whether using paper or common perforated index cards. Card printing is available for stories, defects, test sets, tasks and tests.

Defects and Test Sets in Epics

summer_'12_Epic_Bubble_Chart.pngLet's face it, sometimes the development of new features necessarily involves overcoming debts incurred in the past. Sometimes the development of new features means we need to be extra careful about regression testing features already delivered. Now your epics can account for this "collateral work" by pulling in existing defects and test sets to fully account for the true effort in your plans. Defects and test sets can be associated with an epic by editing the field in a grid, editing through the lookup, or by using the new multi-select Move To Epic option on the Backlog page in Product Planning. Epic views, filters and reporting output include stories and any associated defects and test sets as well.

Epic Bubble Chart

Have lots of ideas for big features, but trouble figuring out what to do first? The classic strategic bubble chart helps the organization to identify the epics that are most worthy of development. The chart separates epics by cost, value, risk and assessed priority making it easy to see and go after the biggest bang for the buck. It shows all top level epics (called 'tracking epics') for the selected project, making it easy to compare top level business initiatives or lower level features. The epic bubble chart is available inline directly from the Epic Board view and can also be accessed from the reports section.

Datamart Updates

Improved Epic Reporting

Now that you've leveraged the power of multi-level strategic planning in VersionOne, you have sufficient data to create some meaningful reports. Starting in the Summer 2012 release, the Data Mart database contains a new Fact table that allows you to trend changes to your Epics over time. This new table, Fact.Epic, contains the data necessary data to support trending on Epic relationships, such as Epic Status, Epic numeric fields, such as Swag, and Custom Numbers, Dropdowns and Checkboxes fields on Epics. It also contains the following roll-up measures: Total Estimate, Open Estimate, Closed Estimate, Total Workitem Count, Total Open Workitem Count, Total Closed Workitem Count, Total Unestimated Workitem Count, and total Effort.

In addition to those changes, the data mart also enables reporting on Defects and TestSets related to Epics. Starting in the Summer 2012 release, the Epic relationship fields on Dim.PrimaryWorkitem, Fact.PrimaryWorkitem, and Fact.Workitem are now populated for Defects and TestSets. With this change, SQL queries on the Epic relationship will now include Defects and TestSets related to the Epic.

Data Mart Schema Change

The enhancement to support Custom List types and Custom Check-boxes with the same name required a change in the Data Mart database schema. Starting with this release there is a new dimension table, Dim.BooleanAttribute. This dimension is used for all Custom Check-box fields defined in VersionOne. The ETL will no longer create a dimension table for each Custom Check-box.

Fixes

  • Fixed: ETL fails when a Custom Field name in the VersionOne instance matches the name of a built-in field for the same data type.
  • Fixed: ETL fails when a Custom List type has the same name as a Custom Check-box.

Analytics Updates

Improved Epic Reporting

Now that you've leveraged the power of multi-level strategic planning in VersionOne, you have sufficient data for reporting; and probably some customers asking for reports. The Summer 2012 has several new features that allow you to deliver. First, there is a new spreadsheet-style Analytic Grid targeted to Epics. With this grid you can perform analysis of your Epics, including performing calculations, as-of-date shifts, filtering and graphing output. Next, we've added a new data object in Custom Reporting called "Epic Trends" that allows users to create Custom Reports that trend changes to VersionOne Epics. This object allows users to report on changes to Epic attributes and the creation of Custom Reports that trend the following measures: Total Estimate, Open Estimate, Closed Estimate, Total Workitem Count, Total Open Workitem Count, Total Closed Workitem Count, Total Unestimated Workitem Count, and total Effort. Finally, the Epic relationship field on the "Workitem Details" and the "Workitem Trends" data objects is populated for Defects and TestSets. Any new or existing report definition based on the Epic Relationship will now include Defects and TestSets related to the Epic in VersionOne.

Analytic Grids have links to Asset Details Pages

Updating VersionOne from the Analytic grids became easier with the Summer 2012 release. Clicking on the ID or Title of an Epic, Story, Defect, TestSet, Task and Test will open the VersionOne detail page of that object.

Data Mart Schema Change

In this release, there is a change in the Data Mart ETL in order to support custom check-box fields and custom list types with the same name. This change will impact existing custom report definitions that are based on custom check-box fields. The Custom Reporting UI will indicate that these reports need attention and provide instructions on how to modify the report.

Fixes

  • Fixed: An issue that prevented users from creating Custom Reports on Workitems without Owners. This change involved adding two new relationships to Owners and deprecating the existing relationships. Please take time to update any existing report definitions to use the new relationship and contact VersionOne support if you cannot use the new relationship in your report. Unless we hear of an issue, we will remove the deprecated relationship next year.
  • Fixed: An issue that prevented users from creating Custom Reports on Workitems without Goals. This change involved adding two new relationships to Goals and deprecating the existing relationships. Please take time to update any existing report definitions to use the new relationship and contact VersionOne support if you cannot use the new relationship in your report. Unless we hear of an issue, we will remove the deprecated relationship next year.
  • Fixed: App pool expects 32 bit support enabled.
  • Fixed: Inaccurate error message if Analytics cannot connect to Data Mart database.

Platform Updates

.NET SDK

  • Added: Range search for numeric values in Object Model.
  • Fixed: Epics in the Object Model can have Tests as children.
  • Fixed: Epic.Risk is a Number, not a List value.
  • Fixed: DateTime formatter for filters should not drop milliseconds.

Java SDK

  • Added: Range search for numeric values in Object Model.
  • Fixed: Epics in the Object Model can have Tests as children.
  • Fixed: Epic.Risk is a Number, not a List value.
  • Fixed: DateTime formatter for filters should not drop milliseconds.

Git Integration

  • Fixed: Links for multi-repository.

Eclipse Integration

  • Added: Support for Eclipse 4.2.

Visual Studio Team System Integration

  • Fixed: Performance problem on check-in page for VersionOne instances where there are many open sprints.

API Changes

VersionOne business rules now allow for Epic.Sub to include Defect and TestSet. Conversely, Defect.Super and TestSet.Super can be set to an Epic.

System Requirements Changes

Latest browser updates:

  • Chrome 20
  • Firefox 14

Minimum server configuration updates:

  • Processor: Dual-Core 2GHz
  • Memory: 4 GB RAM

Miscellaneous

  • Link and attachments on parent epics now display on any defects and test sets contained by the epic.

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

  • Collect initial project and sprint information on a new Application Setup landing page (new Catalyst Edition installations only).
  • Catalyst landing page allows the admin to define member profile settings.
  • Improved layout for Invited Members landing page.
  • Improved content and styling on the Catalyst Admin Overview page.
  • Added support for explicit logout when using SSO.
  • Improved profile memory management and other various performance improvements.
  • Was this article helpful?