Summary:

Currently, the Jira Connector uses a timer mechanism for pushing updates from Jira Align to Jira. If a push fails and the work item remains unsynced for more than 24 hours, it becomes "stale" and requires manual intervention to resume syncing. This can result in missed data if the connection between Jira Align and Jira is lost for more than 24 hours.

Suggestion:

Please review and consider extending the 24-hour staleness threshold for the "push to Jira" timer. The current 24-hour cutoff can lead to data loss or require manual recovery actions if there is a prolonged outage or connectivity issue between Jira Align and Jira. Extending this window (or making it configurable) would help ensure that no data is missed in scenarios where the connection is lost for more than 24 hours, improving reliability and reducing the need for manual intervention.

Background & Impact:

• The connector currently tracks the LastModifiedDate and will not push issues from Align to Jira if this timestamp exceeds 24 hours, resulting in stale items that require manual sync
• Outages or extended sync failures (e.g., due to network issues, maintenance, or large data loads) can easily exceed 24 hours, especially for large customers with high sync durations
• Making the staleness threshold configurable or extending it would help prevent data loss and reduce operational overhead for both customers and support teams.