Rollup Fields for Jira · Documentation · Support · Privacy · Security · Terms
Rollup Fields for Jira: Security
Version 2.0.0, 19 November 2026.
Architecture
An Atlassian Forge app (UI Kit admin page plus issue event triggers) running on Atlassian infrastructure. The only data it stores is the rollup configuration and a short error log (field id, issue key, error text), in Forge app storage. It has no database and no server of ours.
Data and egress
The app declares no external egress and calls no external services. Issue data is read from your own site through the Jira API, and the computed value is written back to your own Jira field.
Permissions
read:jira-work: read issues, issue links and search results to compute totals.write:jira-work: write the computed value into the rollup field.storage:app: store the rollup configuration and the error log.
Controls
Only Jira administrators can change the configuration, checked on every call. Field ids are accepted only if Jira itself lists them. Aggregation and source types are checked against fixed lists. Issue keys are checked by pattern before they reach a query, link type names are escaped, and values are type checked before they are summed. The optional JQL filter is entered by an administrator, added to the query as an extra condition and validated by Jira. Screens are rendered through React, which escapes text. Dependencies are scanned with npm audit (no known vulnerabilities at release).
Report a vulnerability
Write to security@zenthas.com. Please include the app version and steps to reproduce, and no customer data. We aim to acknowledge reports within 2 business days (Germany), without a guaranteed response time.