Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.dsalta.com/llms.txt

Use this file to discover all available pages before exploring further.

The Changes page tracks change management across your organization — from feature deployments to infrastructure updates. Changes can be synced automatically from connected project management tools or created manually.

​
How changes are tracked

Changes flow into DSALTA from two sources:
  • Integration-sourced — When you connect project management tools like Asana, Linear, Trello, or GitHub Issues, change request tickets sync automatically. Each record shows the integration name as its source.
  • Manual — Your team can log changes directly in DSALTA. Manual changes show Source: Manual.
Both types appear in the same table and are treated identically during audits.

​
Change details

Each change displays:
ColumnDescription
TitleName or summary of the change
TypeFeature, Bug Fix, Infrastructure, Security, or Emergency
StatusDraft, In Review, Approved, Deployed, or Rolled Back
PriorityCritical, High, Medium, or Low
EnvironmentProduction, Staging, Development
RequesterWho requested the change
ReviewerWho approved or reviewed the change
SourceIntegration name or “Manual”
Click any change to view the full detail page with:
  • Description — What the change does and why it is needed
  • Rollback plan — Steps to revert the change if issues arise
  • Approval history — Who reviewed and when they approved
  • Timeline — Status changes with timestamps
  • Related assets — Systems or services affected by the change

​
Working with changes

To create a new change manually, click + New Change and fill in the required fields. Assign a reviewer and set the priority level. Changes follow an approval workflow:
  1. Draft — Change request created, not yet submitted for review
  2. In Review — Submitted to a reviewer for approval
  3. Approved — Reviewer approved the change
  4. Deployed — Change has been implemented in the target environment
  5. Rolled Back — Change was reverted due to issues
Each status change is logged with a timestamp and the user who made the change. Auditors use this trail to verify that changes follow your organization’s change management policy.

​
Integrations that feed Changes

Connect these integrations to automatically sync change management tickets into DSALTA:
IntegrationWhat syncs
AsanaTasks and projects used for change tracking
LinearIssues and projects
TrelloCards and boards
GitHub IssuesIssues tagged for change management
To connect an integration, go to Integrations in the DSALTA sidebar.