How it works: data, storage & security
How Connected Table works under the hood — written for IT, security reviewers, and technical administrators evaluating the app.
Built entirely on Atlassian Forge
Connected Table is a Forge app. It runs inside Atlassian’s own cloud infrastructure — there is no external server, no third-party hosting, and no separate database. The app’s code executes on Atlassian-managed infrastructure and in your browser; nothing is deployed to or operated by the vendor outside Atlassian’s cloud.
Where your data is stored
Each table is stored in the Jira issue’s own field value (and, on Jira Service Management, in the portal request). It lives with the issue, inside your Jira instance, and is backed up, exported, and access-controlled exactly like any other Jira field data.
- No external or vendor-side data store is involved.
- The table travels with the issue (clones, exports, and the issue’s own history include it).
- Because the whole table is held in one field value, there’s a practical size ceiling of roughly 100–150 rows per table (depending on the number of columns and how much text each cell holds).
What the app can access
At install, Connected Table requests a small set of permissions. In plain terms:
| Permission | Why it’s needed |
|---|---|
| Read & write Jira work (issues) | To read the table from an issue and save your edits back to it. |
| Manage Jira configuration | To provide the custom field and its per-context column configuration. |
| App storage | Standard Forge app storage for app-level settings. |
| Read Jira user directory | To power the user-picker column type (search and select a Jira user). |
The app accesses only Jira/JSM data it is granted at install — nothing outside your Atlassian environment.
How it’s processed
The interactive grid and all in-table computation (formulas, aggregation, sequence numbering) run in your browser. There is no external computation service; formula evaluation is sandboxed client-side.
Where the table appears
| Surface | Behaviour |
|---|---|
| Issue view — field cell | Click to edit inline. |
| Issue view — Apps panel | Always-on grid in the main content area (read-only → Edit → Save). |
| Activity — Connected Table History tab | Read-only, row/cell-level change log built from Jira’s own history. |
| JSM customer portal — request detail | Read/edit panel for customers and unlicensed users. |
Change history & auditability
Every edit to a table is captured in Jira’s own issue history, and surfaced as a readable row/cell-level diff in the Connected Table History activity tab. Nothing is stored outside Jira to make this work.
Updates
The app is delivered and updated through the Atlassian Marketplace / Forge app lifecycle. Administrators review and approve any permission changes as part of the standard upgrade flow.