Keelcroft / GitHub Issues Sync for Jira / Data deletion

Data deletion

Effective 27 September 2026. October 27 release-candidate clarification, DEV 2.22; production pending. Retention and deletion limits below distinguish pair unlinking, pause and installation-wide uninstall.

Delete one linked pair

In the next release, open Project settings, Apps, GitHub Issues Sync for Jira, then Reconciliation, Unlink pair and Confirm unlink. The app removes the link record and both lookup entries, not either issue or its copied comments. The existing issue-panel Unlink is another pair-removal path. Unlink does not erase the connection, optional assignee mapping or event history.

A matching trigger label may cause relinking. Remove the trigger label or change the automatic-creation rule if you do not want that issue paired again; unlink alone is not a permanent exclusion.

Stop all syncing without deleting

In Project settings, open GitHub Issues Sync for Jira and choose Pause sync. This disables the connection for further sync processing and clears the webhook signing secret. It also asks GitHub to delete the webhook; if GitHub rejects that request, remove the stale hook in repository settings as the app instructs. Pause does not delete the stored personal access token, connection settings, optional assignee mappings, links or event history, and cannot undo completed writes.

Remove installation data or ask about manual removal

There is no general disconnect/delete-connection control. For removal questions limited to one project, contact support rather than assuming pause or unlink deletes everything. Uninstall applies to the installation, not just one project. Pause configured connections first where possible, remove any stale GitHub hooks, then uninstall. Atlassian's hosted-storage retention/deletion window is 0–28 days after uninstall, not immediate erasure.

What is deleted, and when

• Link record and lookup entries for one pair — removed when you unlink that pair; copied content, connection settings/mappings and historical event entries are not removed by unlink.
• The webhook signing secret — immediately, when you pause sync. The GitHub webhook is also deleted when GitHub accepts the request; otherwise remove it manually.
• Event journal entries — 90 days after their last write, automatically.
• Connection settings, optional Jira account ID/GitHub login mappings and remaining links/indexes — durable with no automatic TTL, until relevant settings are replaced/manually removed or Forge data is deleted following uninstall.
• Comment-copy claims — metadata keys and timestamps, not comment text; normally removed after a pass. Stale claims can be reclaimed after 10 minutes, but that is not a guaranteed automatic-deletion TTL.
• The stored token — kept through pause; replaced/manually removed or deleted with Forge data following uninstall. The token must still be revoked separately in GitHub.
• Remaining installation data, including encrypted secrets — subject to Atlassian's 0–28-day hosted-storage retention/deletion window after uninstall.

Things only you can remove

• The token. The app cannot revoke your personal access token, and uninstalling does not revoke it. Revoke it in your GitHub developer settings. Do this first if you believe it has been exposed.
• The setup-check issue. GitHub's REST API cannot delete an issue, so the disposable issue is closed rather than removed. Delete it from the GitHub web interface if you want it gone.

Ask for a deletion in writing

Email support@keelcroft.com with your Jira Cloud hostname and the Jira project key. Requests are answered within two business days. Never include a token in the request.