Admin Guide

This guide is for Jira administrators installing and configuring Connected Table.

Installing the app

1. Install Connected Table from the Atlassian Marketplace.
2. Approve the requested permissions at install: read & write Jira work, manage Jira configuration, app storage, and read the Jira user directory (for the user-picker column).

Adding the field to issues

1. Go to Jira settings → Issues → Custom fields.
2. Create a custom field and choose Connected Table from the field-type list (it appears like any built-in type). You can create multiple independent instances of it.
3. Associate the field with the relevant screens (see placement guidance below).

Configuring columns & defaults

Column configuration is done through Jira’s native field-context system (not a separate admin page). When you edit a field context, Connected Table shows its column editor:

• Add columns and set each one’s type (text, number, checkbox, date/time, selection, user, formula, sequence).
• Mark columns required — enforced on save/create (see below).
• For selection columns, define the option list.
• For formula columns, write an expression that computes from other columns.
• Set default rows that new issues start with.
• Optionally enable “Allow viewers to switch layout” so users can toggle grid/transposed view.
• Optionally toggle “Allow viewers to merge cells within a column” and “Allow viewers to drag-fill cells down a column” — the spreadsheet-style merge and drag-to-fill actions. Both are on by default; turn either off to lock it down for a given field.

Because contexts are per-project/issue-type, the same field can carry different columns in different projects.

Required-column enforcement

Marking a column required makes Jira block save/create when any row leaves that column empty, returning: “Please fill in all required table columns before saving.” This is enforced automatically on the standard edit/create path — no separate Jira “Required” field-configuration setting is needed.

Note

On the panels and the JSM portal, required columns are enforced by the app’s own checks before saving.

Where the table appears

Surface	Notes
Issue-view field cell	Blank until clicked (click-to-edit). The grid does not render in the cell itself — use inline edit or the Apps panel.
Apps issue panel	Always-on grid in the main content area, opened from the issue’s Apps/gear menu.
Connected Table History activity tab	Read-only per-issue change log.
JSM portal request detail	Read/edit panel below Activity; visible to customers and unlicensed users.

Hiding the field label / cell

The app can’t remove itself from the issue view. If you want to hide the field’s label row, hide the field via the project’s issue layout configuration. The panels still read and write the value regardless of layout.

Screen-placement guidance

Keep Connected Table off classic/legacy transition screens

On the modern transition dialog the grid renders and is editable. On classic transition screens the field falls back to a raw text field that is editable and therefore corruptible — a bad hand-edit writes invalid data straight to the field. Don’t add the field to classic transition screens (JSM/agent, bulk, and board-triggered transitions commonly use them).

Data size limits

Note

The entire table is stored in a single field value, so keep tables to roughly 100–150 rows (depending on column count and content). Much larger tables can’t be saved. Merged cells add a small amount of data, so they count toward this too.

Admin page

The app ships a Connected Table Admin page (under Apps in Jira settings) for app-level configuration.