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.

Checks that all change management tickets have an assignee.

​
Why This Matters

Untracked or unassigned change requests indicate a lack of change management discipline. Without proper tracking, changes can introduce security regressions, compliance violations, or service disruptions without accountability. SOC 2 (CC8.1) and ISO 27001 (A.12.1.2) require documented change management processes.

​
What DSALTA Checks

DSALTA connects to your GitHub environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → GitHub.

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Navigate to your GitHub project board.
  2. Ensure a dedicated project or board exists for change management tracking.
  3. For each change request, ensure it has: an assignee, a description, and a target resolution date.
  4. Review and close stale tickets older than 30 days — either complete the change or close as “won’t do” with justification.
  5. Set up DSALTA to monitor your ticketing system for compliance with change management SLAs.
  6. Once all tickets are properly assigned and resolved within SLA, DSALTA will update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the GitHub integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. The assigned responsible role receives a notification. Remediate the issue before it affects your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment. Remediation actions must be performed by your team directly in GitHub.