|Inline Asset Editing|
|Team Process Management|
|Data Mart Updates|
|System Requirements Changes|
How to Upgrade
|If your system is not in the auto-upgrade program, contact support to be added to the program or to schedule your upgrade.||Apr. 29||Apr. 29||May 6||May 6||N/A|
|Contact support for a new 2017 annual license for your on-site system.||Download||Download||Contact Us|
If you are not a current customer, email us at firstname.lastname@example.org to get started.
Inline Asset Editing
We received a lot of valuable feedback on the VersionOne Lifecycle platform regarding the number of pop-ups, especially when editing asset details. We heard you and we are very excited to announce a big change in how you edit.
You can now update asset details directly on the asset detail view, without having to open the Edit pop-up. Inline editing is a quick and easy way to update any item in-place. It makes the interaction more direct and intuitive as the user can edit the text in the same place it is shown and avoid being directed to a separate edit page.
This feature is available on all editable assets, such as Story, Defect, Task, etc. When hovered over with a mouse, each editable field, including the asset title, shows a border and a pencil icon. This indicates that the field is editable in place. Undo is supported, as well, via CTRL+Z.
New filtering capabilities are the most requested feature in VersionOne IdeaSpace. A lot of comments and ideas involved the ability to select any fields for the filter, not just the ones that are pre-selected. Additionally, you told us that you would like to select multiple values to filter by. In our ongoing effort to improve your Lifecycle experience, we have revamped the way you filter the grids and take it to the next level.
We are thrilled to announce a new streamlined filtering experience for our grid views. The new filter interface gives you the ability to quickly add any available field and include multiple values for each field for data specific to your needs.
While the previous filter limited you to one choice, the new filter allows you to filter by more than one Owner, Team, or even Priority. We hope that you'll enjoy this simpler, but much more powerful user interface. Stay tuned for even more filter improvements in upcoming releases! To learn more, see Filtering a Grid.
Teams Can Manage Their Process
Team autonomy and self organization are key concepts in agile development. A prescribed process is a great way to get started with agile development, but as teams mature, they frequently need to adjust the process to meet their needs. Prior to this release, any process change relied on a central administrator to manage a global list of status values and enable them in project workspaces. This arrangement works well, but can be cumbersome in large organizations. It also requires that the people managing work across multiple teams understand team-specific details within the scope of the big picture.
Not anymore! Beginning in Spring 2017, VersionOne Lifecycle can be configured to give teams the ability to independently define and manage their own process while providing cross-team managers and stakeholders visibility into the work being delivered. This change reduces the burden on system administrators and avoids the need to understand the intersection between status values and project workspaces. When a team defines a process, that process is used for all backlog items owned by the team, regardless of where the backlog item resides in the project/planning hierarchy. Backlog Items assigned to a team without a defined process follow the process defined in the project workspace. Backlog items not assigned to any team also follow the process defined in the project workspace. All of this power is controlled by the Team Workspace checkbox on the System Configuration tab in Administration. The Team Workspace feature is disabled by default when upgrading an existing instance and enabled by default on new instances.
When the feature is enabled, a Process tab is visible on the Team Details page. This tab is where you define and manage the team-specific process. Teams that define a process, see and use their status values on backlog items they own; on Storyboards, filtered to the team; in the Grid Status filter when a Grid is filtered to the team; and on Status-based reports, such as Cumulative Flow and Cycle Time, when the report filtered to the Team.
For individuals focused on work across multiple Teams, all status values map to a single Roll-up Category (previously called Reporting Category) that indicates if the Backlog Item is Not Started, In Progress, or Complete. Storyboards and Cumulative Flow diagrams use these categories when considering backlog items that depend on multiple processes.
For additional details, refer to the Team Process Management help article and check out the videos referenced there.
In support of the Team Process Management feature, the Data Mart database and ETL program were modified as follows:
Added a Team Key and Team Name column to Dim.WorkitemStatus. These columns indicates which Team owns the value when a Status value is part of a Team Process.
Added a Scheme Key and Scheme Name column to Dim.Project. These columns indicate which Project Workspace is assigned to the Project.
Added a new Table Dim.Scheme for current Project Workspace information.
Added a new Table Bridge.ListValuesInScheme which is used to relate all list values to the scheme where they are used.
Added a stored procedure sp_GetValidStatusValues to return the list of valid status values for a given Project, Program, and Team. This stored procedure is used by panels in Analytics to populate status value drop downs.
In support of the Team Process Management feature, the following changes were made to Analytics
The Workitem Cycle Time Details panel was updated to honor the selected Team when choosing the Status values that define the Cycle.
The Workitem Cycle Time Summary panel was updated to honor the selected Team when choosing the Status values that define the Cycle.
The Workitem Cycle Time Histogram panel was updated to honor the selected Team when choosing the Status values that define the Cycle.
The Workitem Time In Status panel was updated to honor the selected Team when choosing the Status values that define the Cycle.
The Workitem Time In Status Histogram panel was updated to honor the selected Team when choosing the Status values that define the Cycle.
Added a Bin parameter to the Workitem Time In Status Histogram panel to enable grouping of results into larger date ranges.
Members cannot always see Dashboards that are shared with them. This condition disables all Dashboard shared with that Member.
Member Group Names containing an apostrophe result in errors when sharing Dashboard Panels.
A dedicated place for developers, data analysts and the like to experiment with the Lifecycle API. Use this A person would consider using this console if they are trying to query Lifecycle for custom reporting purposes. Another scenario could be a developer introducing themselves to the API prior to writing code for an integration. Get and Post operations can be performed on live data, support also exists for XML and JSON.
Exercises have been created to help introduce you to the Lifecycle API and the API Console. Refer to the VersionOne REST API Tutorial to get started.
- To access your instance's API Console, add /ApiConsole.mvc to your instance URL (e.g., https://www8.v1host.com/MyCompany/APIConsole.mvc).
Added Support for VSTS - TFVC
Flow & Risk Dashboards
Continuum now features new metrics dashboards that provide invaluable information on the flow and risk of your devops implementation.
New metric dashboards provide key insights into the performance of your software delivery operation, allowing you to identify areas for opportunity and improvement as well as analyzing the impact of changes in devops processes.
"Flow" metrics provide key data around the movement of software across your value stream while "Risk" metrics provide feedback on commit distribution, rogue commits, and risk averages.
Progression Activities and Controls
Continuum now offers the ability of clearly defining devops processes through the configuration of custom activities and controls that define how software moves through your value stream.
Define automated or manual activities for software packages to be executed as they move through a progression; following the same process every time, thus ensuring release consistency.
Evaluate the output of configured activities through custom controls and optionally move packages automatically through you value stream.
Add consistency and speed to the release process while creating consistent processes for audit and control.
Enhanced Manual Interactions
Manual interactions can now be assigned to individual users in addition to tags (groups). Manual interactions trigger email notifications to alert users or tags when an interaction needs their attention.
Risk Metrics - Defects by Source File & Risky Files
Audit risk for individual files in your version control system and see which workitems participated in the changes attributed to specific files.
Identify files/projects with high risk and see all files changed by a package revision.
Pipeline instance page now offers infinite scroll
Manual interactions now allow custom responses which can be passed as arguments elsewhere
“delete-progression” command has been added
“delete-progression” API call has been added
Pipeline instance page hyperlinks issues have been corrected
Jenkins build details can now be saved on every scenario
Package revision with no artifacts now calculate risk properly
For ALM Connect customers that require the need to track effort for CapEx/OpEx reporting, support for Jira work logs and Lifecycle actuals have been added to ALM Connect.
For customers using Slack for team collaboration; notifications, comments and other actions are now supported.
For ALM Connect customers using ALM Connect between a version control system and Lifecycle; ALM Connect will now create Commits (formally Changesets) in Lifecycle for the corresponding asset IDs mentioned in the code commit.
Contact us for upgrade details to utilize these new features.
System Requirements Changes
No changes. See Lifecycle System Requirements for details.
When adding a new asset to a grid, default values are automatically populated from the grid filter, so that when the asset is saved, it shows up in that grid.
Searching for a user to mentions will no longer include Change Sets made by the user in the search result set. (This used to clog the results with every change set by the user).
The side panel on the asset detail view automatically collapses if the view is too small, making it easier to see important asset details.
For a complete listing of point releases, see Point Release Notes by Product.