Zenthas

Reminders: Security

Version 0.1.0, 13 November 2026.

Architecture

A Forge UI Kit app on Node.js 22. Modules: issue panel, global page, project settings page, a scheduled trigger every 5 minutes (the Forge minimum), an async-event queue consumer and one resolver. Reminders live in the Forge key-value store.

Data and egress

The app declares no external egress and talks only to Jira through the Forge API. Stored data is listed on the Privacy page.

Permissions

read:jira-work: read the issue (title, status, assignee, reporter).
write:jira-work: send the notification and, if switched on, add a comment that mentions the recipients.
read:jira-user: look up display names, groups and the user's time zone.
storage:app: keep reminders and the per-project switch in Forge storage.

Controls

Profile, group and issue-visibility checks run as the calling user, so nobody can set reminders on issues they cannot see. Sending and the "issue resolved" check run as the app, because the reminder fires without a user present. A reminder that adds an issue comment is only stored if the user may comment on that issue (Add Comments permission, checked as the user). The app uses asApp only in the queue consumer that sends reminders. Only the creator can delete a reminder, and only project administrators can switch a project off. Sending is idempotent, inputs are length-limited, issue keys are URL-encoded and mail HTML is escaped.

Known limits

Timing is checked every 5 minutes. Email goes through Jira notifications, so free-form addresses are not supported. The overview scans up to 1000 entries per status.

Report a vulnerability

Write to support@zenthas.com. We acknowledge every report, and fixes ship as new app versions through Atlassian Marketplace.