In the Advanced edition, readers can edit fields in the table. Each change is saved as the reader, so Jira applies their permissions, screens and validation as usual. It is off until a page editor turns it on.

Turn it on

Open the macro’s configuration
Edit the page, select the macro, then the pencil icon on it.
Switch on Allow inline editing
It appears under Results per page, in the Advanced edition only.
Leave out the columns that should stay read-only
Each editable column has an Editable switch in Column options, on by default.
Save, then publish the page
Nothing is editable while the page is open in the editor.

Who can edit

A reader gets editors when all of these are true:

The subscription is the Advanced edition.
The macro has Allow inline editing on, and the column has Editable on.
The reader is signed in with a Confluence licence. Anonymous and unlicensed readers see the table only.
The page is being viewed, not edited.
Jira lets this reader edit this field on this work item, checked each time a cell opens.

Otherwise the cell says You can’t edit this field on this work item., with a link to Jira.

What the edition check protects

The edition check runs in the browser and guards the paid feature, not your data. Every change uses the reader’s own Jira permissions. The app never saves as itself.

Edit a cell

Select the cell. In a cell full of links, select the pencil at its right edge.
Change the value. It is checked as you type where the field has rules.
Confirm to save.

The row redraws from what Jira stored, without a reload.
A work item that no longer matches the JQL stays until the page reloads.
If Jira refuses, the cell keeps its old value and shows Jira did not save the change: and the reason.
One cell is open at a time.

What can be edited

Field	Editor
Summary, Short text, Epic Name	Text
Number, Story points	Number
URL	Text, checked as an address
Due date, Date picker, Target start and end	Date
Date time picker	Date and time, in the reader’s browser time zone
Priority, Single select, Radio buttons, Version picker	A list of the values Jira allows
Multi select, Checkboxes, Components, Fix and Affects versions, Multi version picker, Flagged	A list, several values
Cascading select	Two lists: the parent, then a child under it
Labels	Existing labels as you type, or a new one
Assignee, Reporter, User picker	A user picker
Multi user picker, People	A user picker, several users
Parent	A search of work items
Original estimate, Remaining estimate, Time tracking	A time such as `2h 30m` or `1d`
Status	The statuses the work item can move to
Assets objects	A search of Assets objects
Work Item Selector, single select	A search of work items, subtasks included
Work Item Selector, multi select	A search of work items, several, subtasks included
Description, Environment, Paragraph	A rich text editor in place of the cell

Field by field

Status leaves out transitions whose screen needs a field without a default. Other fields the transition sets show after a reload.
People lists every user. Jira refuses someone who cannot be assigned, with the reason.
Labels cannot contain spaces or be longer than 255 characters.
Estimates: Jira cannot clear one, so use 0m for none.
Parent offers non-subtasks. Jira refuses the wrong level, with the reason.
Cascading select: changing the parent clears the child.
Work Item Selector offers any work item the reader can find, with their permissions. The selector’s JQL scope and permission mode do not apply: Jira does not let one app read another’s configuration.
Rich text opens an editor with its own Save and Cancel when the field holds only formatting, headings, quotes, lists, colour, links and code. A table, mention, image or panel means editing in Jira, so nothing is lost.

Assets fields

Search matches the label, the field’s search attributes and the key, 25 objects at a time.
Objects offered when editing (AQL), a column setting, limits the search, such as objectType = Laptop. Jira does not let apps read the field’s own filter. Left empty, it offers the types already on the page first. Jira refuses a disallowed object on save.
One or several objects follows the field’s setting in Jira. A single-object field already holding several keeps the multi editor.
The workspace comes from objects on the page. With none on the page, add one in Jira first.

Assets, Work Item Selector and rich text start from Jira’s current value

Saving replaces the whole field, so the editor reads Jira’s value when it opens. If someone changed it since the page loaded, you see their value first, so you never undo their change.

What is never edited

Set by Jira: Key, Created, Updated, Resolved, Creator, Resolution (set by transitions), Status category changed, Last viewed, Work ratio, Rank.
A move, not an edit: Project, Work type.
Managed elsewhere in Jira: Votes, Watchers, Attachments, Comments, Work log, Subtasks, Linked work items, Time spent, Progress.
Jira Service Management: Request type, SLA fields, Approvals, Satisfaction, Request language.
Fields of other apps: their own app controls how they are edited. Oktul Work Item Selector fields are the one exception, listed above.
Not yet editable: Group pickers, Team, Sprint, Organizations and Request participants. Each needs a scope the app does not have.

Inline editing