Welcome
Release Notes
This document includes information about the new features introduced, defects fixed, and known issues identified in this version of HCL DevOps Velocity (Velocity). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
Known issues
You can find the known issues that are identified in any version of HCL DevOps Velocity (Velocity).

Release Notes
This document includes information about the new features introduced, defects fixed, and known issues identified in this version of HCL DevOps Velocity (Velocity). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
- What's New
  You can find information about the features introduced, enhancements, or other changes made in HCL DevOps Velocity (Velocity). You can also find the features that were introduced in earlier versions of Velocity.
- Defect fixes
  You can find the defects that are fixed in this version of HCL DevOps Velocity (Velocity). You can also find the defects that were fixed in the earlier versions of Velocity. HCL DevOps Velocity is the new name of HCL Accelerate from 5.0.0 onwards.
- Known issues
  You can find the known issues that are identified in any version of HCL DevOps Velocity (Velocity).
System Requirements
This document contains information about hardware and software requirements for HCL DevOps Velocity (Velocity).
Getting Started
This document provides an overview of HCL DevOps Velocity (Velocity).
High-Level Overview
Use HCL DevOps Velocity (Velocity) to automate your release lifecycle and manage your DevOps value streams.
Learning
Learn how to complete frequently-used tasks such as creating value streams.
Managing licenses
Configure your license or apply a trial key.
Administering
This guide describes how to install HCL DevOps Velocity (Velocity). After you install Velocity, you can perform administrative tasks such as license configuration, upgrading, migrating, managing access permissions and security. This guide is intended for system administrators.
Managing Value Streams
A value stream represents the objects and activities that you employ to deliver customer value, from initial concept to final delivered project.
Developing Data Insights
The Insights feature provides DevOps metrics for your project data.
Releasing Software
A release is a repeatable plan that is used to drive deployments.
Extending Product Functions
Learn how to extend the function of HCL DevOps Velocity (Velocity)
How to
The topics in this section describe how to work with HCL DevOps Velocity (Velocity) features. Tutorials and workbooks are available for users of all experience levels.
Troubleshooting
Before you contacting support, gather background information and perform tasks that will assist in solving the problem. It helps to be as specific as possible and include all relevant information.
Notices for DevOps Velocity
This document provides information about copyright, trademarks, terms and conditions for the product documentation.
DevOps Velocity GDPR statement
General Data Protection Regulation (GDPR) has been adopted by the European Union (EU) and applies from May 25, 2018.
Glossary

Known issues

You can find the known issues that are identified in any version of HCL DevOps Velocity (Velocity).

Known issues in Velocity

Known issues in Velocity are as follows:


S. No	Applicable version	Description
1	5.1.0 to 5.1.7	Bitnami images repository locations are changed. You may encounter with `ImagePullBackOff` error for `nginx` and `rabbitmq` pods To work around this problem, you must change the bitnami images respository location by editing the following Kubernetes resources: `accelerate-router` Deployment: Change `bitnami/nginx` to `bitnamilegacy/nginx` in spec/template/spec/containers/image `accelerate-rabbitmq` Statefulset: Change `bitnami/rabbitmq` to `bitnamilegacy/rabbitmq` in spec/template/spec/containers/image
2	5.1.4	When you change the sprint name after the sprint is created, the accuracy of the Agile Churn metric calculation is impacted. To work around this problem, you must archive or close the current sprint and create a new sprint with the updated name. To ensure the accuracy of the Agile Churn calculation, avoid changing the sprint name after the sprint is created.
3	5.1.4	When an issue is moved from Sprint 1 to Sprint 2, which is active, and then to the backlog, this process creates a duplicate Agile Churn metric for Sprint 1, which is already closed. There is no workaround available currently. You should ignore the Agile Churn metric calculated for the Sprint 1, which is already closed, and consider the Agile Churn metric calculated for the Sprint 2 which is active.