Ivo Oskamp
f3b1b56b6a
When a new run is created, Autotask tickets were not being propagated if the associated internal ticket was resolved. This caused users to have to manually re-link tickets on each new run. The previous implementation relied on finding an open internal ticket first, then using its ticket code to find a matching Autotask-linked run. If the internal ticket was resolved, the Autotask propagation would fail. This commit implements a two-strategy approach: 1. Strategy 1: Use internal ticket code (existing logic, improved error handling) 2. Strategy 2: Direct Autotask propagation - find most recent non-deleted Autotask ticket for the job, independent of internal ticket status Now Autotask tickets remain linked across runs regardless of internal ticket resolution status, matching the behavior of internal tickets. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| architecture.md | ||
| autotask_rest_api.md | ||
| backupchecks_autotask_integration_functional_design_living_document.md | ||
| backupchecks_autotask_integration_implementation_breakdown.md | ||
| backupchecks_autotask_integration_phase_2_implementation.md | ||
| changelog-claude.md | ||
| changelog.md | ||
| manifest.md | ||
| migrations.md | ||
| reporting-proposal.md | ||