How changes are tracked
Changes flow into DSALTA from two sources:- Integration-sourced — Two integrations write to this page: ServiceNow and LaunchDarkly. Each record shows the integration name as its source.
- Manual — Your team can log changes directly in DSALTA. Manual changes show Source: Manual.
If your change process runs through a project management or issue-tracking tool, record those changes with Create Changes and put the ticket link in the description — auditors treat manual and synced records identically.For evidence about merged code — pull requests, reviews, branch protection — connect GitHub, GitLab, Bitbucket or Azure DevOps and see Code Changes, which those integrations populate automatically.
Change details
Each change displays:
Click any change to open its detail panel, which has Results, Approval, and Evidence tabs.
Working with changes
To create a new change manually, click Create Changes and fill in the fields: Title (the only required one), Description, Priority, Type, Status, Environment, Rollback Plan (optional) and Testing Notes (optional). Priority defaults to Medium, Type to Infrastructure, Status to Draft, and Environment to All. Changes move through six statuses:- Draft — Change request created, not yet submitted for review
- Pending Review — Submitted to a reviewer for approval
- Approved — Reviewer approved the change
- In Progress — The change is being implemented
- Deployed — Change has been implemented in the target environment
- Rolled Back — Change was reverted due to issues
Integrations that feed Changes
Two integrations sync change records into DSALTA:
To connect an integration, go to Integrations in the DSALTA sidebar.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)