-
You may add a file with commit hash into the software package deployed at customer side. Then you can achieve full traceability with that commit hash, ie. check changes or fixed issues between commit hashe.
-
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Hi,
following a feature idea:
Introduce a feature to manage and track which version of the software (identified by branches or tags) is deployed to specific projects, customers, or machines.
Use Case: In regulated industries like pharmaceuticals, it’s essential to maintain full traceability of software deployments. We are developing software and need a reliable way to document which version (e.g., Git branch or tag) is currently in use at which customer site or on which system. This is important for audit trails, support, and ensuring consistency across environments.
Requested Functionality: • Ability to assign and track a Git branch or tag per deployment instance. • Metadata fields for project name, customer, and target machine/system. • View or report that shows the deployment matrix (which version is deployed where).
Benefits: • Enables complete traceability of software versions in the field. • Supports compliance with industry regulations. • Simplifies support and issue resolution by clearly identifying deployed versions.