Zenthas

Security, Ticket Merge

Stand / Version: 2026-10-22

Architecture

Ticket Merge is an Atlassian Forge app. It runs on Atlassian's platform. It has no server, database or network of its own and makes no calls to any host outside your Jira site. Sign-in, hosting and encryption are provided by Atlassian.

Data

The app stores one record per merge in Forge storage: ticket keys, IDs, status and account IDs. It does not store comment texts, ticket titles, attachments, names or email addresses. Records are deleted after 30 days. No third party receives data. There is no tracking and no AI model.

Access

Preview and merge run with the permissions of the agent who starts them, and the app checks those permissions before it starts. Background steps and undo run under the app account, and the app deletes only items it created itself. Known limit: any agent with access to the app can undo any merge.

Code and dependencies

Inputs such as ticket keys are validated before they reach a request. The interface uses native Forge UI Kit components only. Dependencies are limited to Atlassian Forge packages and React. We run npm audit, forge lint and automated tests before each release.

Incidents and reports

We follow a written incident response plan: triage, containment (rollback to the last good version), fix, customer notice and a written review. Report vulnerabilities to support@zenthas.com with "Security" in the subject. We confirm receipt within 2 business days. Please do not send customer data.

See also: Privacy, Terms, Support.