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.
Can I search or sort a table?
Yes. On the Apps panel and the customer portal, click the magnifier (or press /) to show only rows containing your text. Click any column name to sort ascending, then descending, then back to the original order. Both only change your own view — the saved table is never reordered. See Finding rows: search and sort.
Why don’t my totals match the whole table?
While a search is active, the totals row adds up only the rows you can see. Clear the search to see totals for the whole table.
Can new rows start with values already filled in?
Yes. An admin can set a default value per column — including today’s date or a date relative to today for date columns. See the Admin Guide.
Which formats can I export to?
Excel (.xlsx), PDF, Word (.docx), CSV, and a semicolon-separated CSV for Excel set to a European locale. Click the download icon on the Apps panel or portal panel. See Export & Import.
Does the export include all rows, or just the current page?
All pages. It contains every row matching your current search, in your current sort order, plus the totals row if the table has one.
Which files can I import?
CSV (comma, semicolon or tab separated) and Excel .xlsx, up to 2 MB. Old .xls
workbooks aren’t supported — save them as .xlsx or CSV UTF-8 first.
Does importing save to Jira immediately?
No. Imported rows are added to your unsaved edit. Review them, fix any highlighted cells, then click Save — or Cancel to throw the import away.
Why were some imported cells left empty?
A value couldn’t be read for that column — for example an option that doesn’t exist, an invalid date, or a user name that matches nobody or several people. These cells are highlighted in the preview and imported empty instead of being guessed. For user columns, an email address or account ID is the most reliable.
Are my files uploaded anywhere?
No. Export files are created in your browser and imported files are read in your browser. Only the rows you save are stored, in the Jira issue.
Can I stop users exporting or importing?
Yes. In the field context’s table settings, clear Let viewers export the table or Let users import rows from a file while editing. Import is also hidden when adding and removing rows is locked.
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?
Jira’s built-in History tab records saves made from the Apps panel and the portal under the app rather than the individual user — a Jira platform limitation. The Connected Table History tab shows who actually made each change (for changes saved since September 2026). Your edits are saved normally either way.
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.
- Export and import are available on the Apps panel and the customer portal, not in the inline field editor.
- PDF export covers Latin, Cyrillic and Greek text; use Excel or Word for Chinese, Japanese or Korean.
- Import reads
.csvand.xlsxup to 2 MB;.xlsisn’t supported, and imported rows aren’t merged. - 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.