Oktul Work Item Macro for Confluence
Oktul Work Item Macro shows Jira work items with their Assets objects on Confluence pages, which Confluence's own Jira macro cannot, with any field as a column.
Free for up to 10 users. Larger sites try it free for 30 days.
Ask for a demo (opens in a new tab) We reply within 24 hours, Monday to Friday.
What the video shows
- The title, Jira work items on Confluence pages, beside the macro's table.
- Live from Jira when the page opens: the rows arrive one by one.
- Any field as a column: in Columns, Add column, and Laptop is picked from the field menu.
- With Assets objects as chips: the table gains a Laptop column, each laptop an Assets chip.
- Change a status in the table: a status moves from To Do to In Progress, with the Advanced edition.
- Oktul, Atlassian Marketplace Partner.
Confluence’s own Jira macro leaves out Assets objects
The built-in Jira macro shows no Assets field values
A service team’s status page is about what its work items point at: the servers, laptops and contracts in Jira Service Management Assets. Atlassian records the gap as suggestion CONFCLOUD-80484, open since January 2025.
A pasted export is out of date at once
The workaround is a table pasted from a Jira export. It is stale the moment it is pasted, and it shows every reader what the person who exported it could see.
The macro reads Jira each time the page opens, as the reader
Oktul Work Item Macro for Confluence stores only the JQL query and lets Jira decide what each reader sees. Assets objects appear as chips, beside any other Jira field as a column.
Four things it does on a Confluence page
You set each one on the macro itself. Two tables on the same page can show different work items, columns and options.
Any field as a column
Every field on the site is in the column picker, custom fields and other apps’ fields included. Each column has the display options its field type needs.
Choose the columnsAssets objects
An Assets field shows each object with its object type’s icon, its label linked to the object, and its key, or an attribute of your choice. Assets’ predefined icons are shown, and an uploaded icon appears as a generic one.
Show Assets fieldsPDF and Word export
PDF and Word exports, page history and notification emails carry the list as a Confluence table of up to 300 work items, with links that work outside Confluence. The export runs as the person it is made for.
Export the pageInline editing
In the Advanced edition, readers change fields in the table, from text and dates to Assets objects. Every change is saved as the reader, so Jira applies their permissions, screens and validation.
Edit in the tableJira data on a page, never a stale copy
A table pasted from Jira is the copy an agent quotes after it has gone out of date. The macro stores only the JQL query and reads Jira each time the page is opened, as the reader, with Assets objects and Oktul Work Item Selector fields. The page stays correct without an automation rule or a manual update. In the Advanced edition, readers correct a field in the table and Jira saves it as them.
Read how it worksEvery feature
Compared with the built-in Jira macro
A tick means the app does everything the row describes. Where it does part of it, the cell names what is missing. The built-in macro's column was checked against Atlassian's own documentation.
| Capability | Oktul Work Item Macro for Confluence (opens in a new tab)Oktul | Jira work items macro (opens in a new tab)Atlassian, built into Confluence |
|---|---|---|
| Shows Assets objectsEach Jira Service Management Assets field shows its objects with the object type's icon, the label linked to the object and the key. Confluence's built-in macro shows no Assets field values; Atlassian tracks this as suggestion CONFCLOUD-80484 and documents Assets on a page as a separate macro. | Yes | No |
| Works with other Oktul applicationsOktul Work Item Selector fields show as the same work item cards that app draws in Jira, and can be edited in the table in the Advanced edition. SignPlus prints the table, Assets objects and cards included, in a signed document. | Yes | No |
| Extended inline editingReaders change text, numbers, dates, selects, labels, people, parent, estimates, status, Assets objects, rich text and Work Item Selector fields in the table, as themselves, in the Advanced edition. The built-in macro edits some standard fields, and Atlassian publishes no list of which. | Yes | Some standard fields |
| Rename column headingsA page editor writes the heading of every column, so a custom field called cf_Approver_2 can read Approver. | Yes | No |
| Choose how a field is displayedEach column has the options its field type needs: status as a lozenge or text, people as cards or names, dates as dates or relative time, numbers with decimals and a unit. | Yes | No |
Checked on against each product's published documentation, its Marketplace listing where it has one, and testing. If a row no longer matches what an app does, write to hello@oktul.com (opens a new email) and we will check it again.
The tests every release has to pass
A release ships only when it passes these tests. Before each release and once a month we also scan its code for vulnerable dependencies, leaked secrets and unsafe patterns, and attack its web triggers where it has any.
Automated tests
Every field type, editor and export path.
Test suites
Field types, loading, the table, editing, export and dates.
Installation runs through the Atlassian Marketplace
There is absolutely no infrastructure on Oktul's side. The entire application runs within your Atlassian ecosystem.
- Install from the MarketplaceThe app is installed in Confluence and connected to Jira on the same site, in Atlassian’s own install dialog. It runs entirely on Atlassian Forge.
- Insert the macroEdit a page and type /oktul. The macro is in Confluence’s own insert menu.
- Write the JQL query and choose the columnsAny JQL Jira accepts, with the sort order in ORDER BY. A new macro starts with Type, Key, Summary and Status.
- Allow inline editing, if you want itIn the Advanced edition, one switch per macro, off by default, and one per column.
Host platform and compatibility
- Host product
- Confluence Cloud
- Also needs
- Jira Cloud on the same site
- Runtime
- Atlassian Forge
- Data residency
- Your site’s
- Work items per export
- Up to 300
- Version
- 2.15.0, 04.11.2026
For your security review
Send to your security team (opens a new email)Runs on Atlassian
Atlassian grants this badge to every application that stores data only within your isolated infrastructure and has no external connections.
What the programme requires (opens in a new tab)CSA STAR Level 1
This application is listed in the Cloud Security Alliance STAR Registry at Level 1. We completed the CAIQ Lite questionnaire with all 138 questions, and published it for you or for your security reviewer.
Read the assessment (opens in a new tab)Questions administrators ask
Why does Confluence's Jira work items macro not show Assets objects?
Confluence Cloud's built-in Jira work items macro does not display Jira Service Management Assets fields. Atlassian tracks it as suggestion CONFCLOUD-80484, open since January 2025, and documents Assets on a page as a separate macro. Oktul Work Item Macro for Confluence lists the same work items with each Assets object in its column: the object type's icon, its label linked to the object, and its key or an attribute you choose.
How do I show an Assets field in a table of Jira work items in Confluence?
Insert Oktul Work Item Macro on the page by typing /oktul, write the JQL query, and add the Assets field under Columns with Add column. Each object appears as a chip with its icon, label and key, read with the permissions of the person viewing the page. Jira Service Management with Assets has to be on the same Atlassian site.
How is it different from Confluence's own Jira work items macro?
It shows Assets objects and draws Oktul Work Item Selector fields as work item cards. A page editor can rename every column heading and choose how each field is displayed. In the Advanced edition, you can edit text, dates, selects, people, estimates, status, Assets objects, rich text and Work Item Selector fields in the table. The built-in macro edits some standard fields inline and does none of the rest.
How does Work Item Macro help Rovo and other AI agents?
It replaces the Jira table pasted into a Confluence page, which goes out of date and shows everyone what its author could see. The macro stores only the JQL query and reads Jira each time the page is opened, as the reader, with Assets objects and Oktul Work Item Selector fields. The page stays correct without an automation rule or a manual update. The app runs no AI model and sends nothing to one.
Who can install it?
A site administrator, from the Atlassian Marketplace listing. The app is installed in Confluence and connected to Jira on the same site. It declares no external permissions and shows no consent screen for external data access. A Forge application can take up to a minute to become available after installation.
Does it need Jira?
Yes. Jira Cloud has to be on the same Atlassian site as Confluence, and the app connected to both. Without Jira the macro can be inserted, but it has no work items to show.
Can a reader see work items they may not open in Jira?
No. The search runs as the person reading the page, with their Jira permissions. Two readers of one page can see different rows. Exports and notification emails run as the person they are made for.
Can readers sort the table?
Yes. Selecting a column heading sorts the list through Jira for that reader only, and a reload restores the saved order. Everyone else, and every export, sees the order in the macro’s JQL query.
What does the Advanced edition add?
Inline editing. Readers change fields directly in the table, as themselves, and Jira applies their permissions, screens and validation to every change. Editing is off in every macro until a page editor turns it on. Everything else is in both editions.
What happens to our data if we uninstall?
Nothing is lost, because the app stores nothing of its own. Each macro’s configuration stays in its page, where Confluence keeps it.
Will this application be supported when Atlassian changes the platform?
Yes. Each release is built to work on a Confluence ahead of or behind the rest of Atlassian's rollout, and on a site that has not yet approved a new permission. If a problem still comes up, raise it in the Help Center and we resolve it under the service level agreement.
Oktul's other applications
- Jira and Confluence
Code Studio
Pending Atlassian approval
Write, store and run JavaScript and TypeScript scripts in Jira and Confluence Cloud.
- Jira
Work Item Selector
Allow users to pick work items based on Jira Query Language (JQL).
Free for up to 10 users. Larger sites try it free for 30 days.
- Confluence
SignPlus
Sign a Confluence page, and prove later which version was signed.
Free for up to 10 users. Larger sites try it free for 30 days.
- Jira
Regex Field
Pending Atlassian approval
Jira fields that fill themselves in from the form, and only accept your format.
Jira and Confluence
Start your free trial
All our paid applications have a 30-day free trial and are free for up to 10 users. Pricing and billing run through the official Atlassian Marketplace, so there is no new supplier to onboard.