About
When you connect Linear to DSALTA, the platform syncs your change tickets using read-only API access. DSALTA activates this check when tickets do not meet your change-management requirements.Why This Matters
Untracked or unassigned changes mean nobody is accountable and security regressions can slip through unnoticed. A documented change-management process with clear ownership is required by SOC 2 and ISO 27001.How to Fix
Before you begin- Ensure you have administrator access to Linear.
- In Linear, create a dedicated project or board for tracking change requests.
- Ensure each change has an assignee, a description, and a target resolution date.
- Connect this system to DSALTA so change activity is captured as evidence.
Frequently Asked Questions
How often does this check run?
How often does this check run?
This check runs automatically every 24 hours while the Linear integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
What happens if it keeps failing?
What happens if it keeps failing?
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Can I exclude this check?
Can I exclude this check?
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
Does DSALTA change my Linear configuration?
Does DSALTA change my Linear configuration?
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Linear.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)