Oktul Work Item Selector for Jira
A single- or multi-select Jira custom field that offers only the work items a JQL query returns, with dynamic values for the current user and work item.
Oktul Work Item Macro for Confluence
A Confluence macro that lists the Jira work items a JQL query returns, with any field as a column, Assets objects as chips and PDF and Word export.
Atlassian reviews this documentation before the listing goes live, so there is nothing to install yet. Everything on this page and in the documentation is final.
- List work items with a JQL query
- Choose any Jira field as a column
- Show Assets objects with their icons
- Export the table to PDF and Word
- Edit fields in the table, in the Advanced edition
The problem we solve
Confluence’s own Jira macro leaves out Assets objects
A service or asset team’s status page is about the things its work items point at: the servers, laptops and contracts held in Jira Service Management Assets. Confluence Cloud’s built-in Jira macro does not display Assets field values. Atlassian records it as suggestion CONFCLOUD-80484, gathering interest since January 2025.
The workaround is a table pasted from a Jira export. It is out of date the moment it is pasted, and it shows every reader what the person who exported it could see.
What it does
Four things it does on a Confluence page
Each one is set on the macro itself, so two tables on the same page can show different work items, columns and options.
01 · Columns
Any Jira 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: status as a lozenge or text, people as cards or names, dates as dates or relative time, numbers with decimals and a unit.
02 · Assets
Assets objects as chips
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. Fields of Oktul Work Item Selector for Jira show as the same work item cards that app draws in Jira.
03 · Export
The table in PDF, Word and email
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.
04 · Inline editing
Edit work items without leaving the page
In the Advanced edition, readers change fields in the table: text, dates, selects, people, estimates, status, Assets objects and rich text. Every change is saved as the reader, so Jira applies their permissions, screens and validation.
Setting it up
Installation runs through the product you already administer
There is no Oktul infrastructure to set up, which makes the application simpler to adopt.
- 1Install from the Marketplace
The 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.
- 2Insert the macro
Edit a page and type /oktul. The macro is in Confluence’s own insert menu.
- 3Write the JQL query and choose the columns
Any JQL Jira accepts, with the sort order in ORDER BY. A new macro starts with Key, Summary and Status.
- 4Allow inline editing, if you want it
In the Advanced edition, one switch per macro, off by default, and one per column.
Where it runs
Host platform and compatibility
Data handling and security
Nothing leaves your Atlassian site
The macro reads Jira as the person viewing the page, from their browser, and keeps nothing. Its only saved data is each macro’s configuration, which Confluence stores in the page.
- Egress
- None. No external hosts declared
- Storage
- The macro configuration, inside your Confluence page
- Caching
- None. Every page view reads Jira again
- Oktul infrastructure
- None
- Sub-processors
- Atlassian only, which hosts the app on Forge
- Analytics or telemetry
- None collected
Atlassian grants this badge per application, to apps that store data only on Atlassian's infrastructure and declare no external hosts.
What the programme requires (opens in a new tab)Tested before each release
The tests every release has to pass
These figures belong to this application only. Suite sizes differ between applications.
- Automated tests
- 277
- Every field type, editor and export path.
- Test suites
- 9
- Field types, loading, the table, editing, export and dates.
- Work items per export
- 300
- The export stops there so it finishes inside Forge’s 25-second limit.
Questions
The questions other administrators ask most
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. Because it declares no external permissions there is 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, so two readers of one page can see different rows. Exports and notification emails run as the person they are made for.
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. The work items were always in Jira.
Will this application be supported when Atlassian changes the platform?
Yes. We keep up with every change to the platform, and our partner status lets us support changes in the ecosystem before they are officially released. If a problem still comes up, raise it in the Help Center and we resolve it under the service level agreement.
Pricing
Billed through the Atlassian Marketplace
Pricing, the free trial and billing run through the Marketplace, on the same terms as every other app on your site. The charge lands on your existing Atlassian invoice, so there is no new supplier to onboard, no purchase order and no security review of our payment handling.
The rest of the portfolio
