Skip to main content

Jama Connect Help

Change control with a hotfix branch

Isolate an urgent change in a hotfix branch, document its impact, obtain sign-off, and selectively merge the approved fix.

When to use change control

Use this workflow when you need to manage an unplanned change without disrupting active development. The hotfix branch keeps the change separate while the team reviews its impact and obtains sign-off.

For example, a semiconductor company might receive a field report that a safety-critical microcontroller shuts down unexpectedly under high-temperature conditions. The team can isolate the fix, document the change, and apply it to the certified baseline after approval.

Workflow summary

The team creates a hotfix branch from the approved baseline, documents and implements the change, and compares the branch with the main project. After the change receives sign-off, the team selectively merges the approved fix and deletes the branch.

The workflow includes issue reporting, hotfix branching, change documentation, fix implementation, branch comparison, selective merging, and branch deletion.

Branching capabilities
  • Branch Create

  • Branch Comparison (Diff View)

  • Branch Merge

  • Branch Delete