FAQ & Support
Frequently asked questions
What is Connected Table?
A configurable table custom field for Jira issues and Jira Service Management portals. Each issue gets a grid of typed columns and rows, stored in a single Jira field — no external database.
Where does my data live? Does it leave Atlassian’s cloud?
No. Connected Table runs entirely on Atlassian Forge and stores the table in the Jira issue’s field value. Nothing is hosted or processed outside Atlassian’s cloud. See How it works: data & security.
Do I need a Jira license to use it on the customer portal?
No. The JSM portal panel supports customers and unlicensed users — they can view and edit the table without a Jira license.
Why is the field cell blank on the issue view?
By design. The field cell is intentionally empty; the always-visible grid lives in the Apps panel (agents) and the portal detail panel (customers). Click the field cell to edit inline.
How do I merge cells or fill values down a column?
While editing, click a cell to reveal its drag handle, then drag along the column and choose Fill or Merge. Hold Ctrl/Shift to fill a series (numbers and trailing-number text increment). Works in both grid and transposed layouts; admins can enable or disable each.
I can’t save — it says “Please fill in all required table columns.”
An admin marked one or more columns required. Every row must have a value in those columns before you can save.
Why do my table edits show as made by the app, not me?
Saves made from the panels and the portal are recorded in the issue history under the app rather than the individual user. Your edits are still saved normally.
How do I choose which columns appear?
Through the field’s context (Jira settings → Custom fields → your field → Configure). Column setup uses Jira’s native field-context system, so the same field can carry different columns per project/issue type.
How big can a table be?
The whole table is stored in one field value, so keep tables to roughly 100–150 rows (depending on columns and content). Much larger tables can’t be saved.
A transition screen shows raw text instead of the grid. Is that a bug?
No. The grid renders on the modern transition dialog, but older classic transition screens fall back to a raw text field. Keep the field off classic transition screens (see the Admin Guide).
Known limitations
- The field cell on the issue view doesn’t show the grid — edit inline, or use the always-on Apps panel.
- Classic transition screens show a raw text fallback instead of the grid.
- A practical ceiling of about 100–150 rows per table.
- No public REST API for the field value yet.
Support
See the Support page for how to reach us and what to include in a report.