Skip to main content
Checks that Trello change request tickets are resolved within 30 days.

​
About

When you connect Trello 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 the Trello integration is connected.
Resolve aging change tickets
  1. In Trello, filter for change tickets open longer than 30 days.
  2. Complete and close each one, or close it with a documented justification.
  3. Set a recurring review to keep change tickets within the 30-day window.
Once aging tickets are resolved, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Trello integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
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.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Trello.