# Oktul Work Item Macro for Confluence Show Jira work items on Confluence pages, with any field as a column. A macro that lists the work items a JQL query returns, in the columns the page needs, and shows each one as it is in Jira when the page is opened. Every request runs as the person reading the page, so Jira decides what each reader sees. Assets objects appear as chips, Work Item Selector fields as work item cards, and the table goes into PDF and Word exports. - **Host:** Confluence Cloud - **Version:** v2.0.0 - **Documentation:** https://oktul.com/docs/plugins/work-item-macro/install/ ## 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. ## 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. ### 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. ### 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. ### 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. ### 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. ## Installation runs through the product you already administer 1. **Install 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. 2. **Insert the macro** Edit a page and type /oktul. The macro is in Confluence’s own insert menu. 3. **Write 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. 4. **Allow inline editing, if you want it** In 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 - **Editions:** Standard, and Advanced with inline editing ## 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 **Scope / What it is for** - `read:jira-work` — Run the macro's JQL query, read the fields each row shows, and load what the inline editor offers. - `write:jira-work` — Save an inline edit or a status transition, as the viewing user, in the Advanced edition. - `read:cmdb-object:jira` — Show an Assets object by its label, and search objects in the inline editor. - `read:cmdb-icon:jira` — Read the names of Assets' predefined icons, so each object chip shows its icon. **Runs on Atlassian.** 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](https://developer.atlassian.com/platform/marketplace/runs-on-atlassian/) ## The tests every release has to pass - **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. ## 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. --- ## Published by - Oktul OÜ - Oktul OÜ · Reg. nr 17589681 · Tallinn, Harjumaa, Estonia - Email: hello@oktul.com - Web: https://oktul.com/ - Atlassian Marketplace: https://marketplace.atlassian.com/vendors/534484195 - LinkedIn: https://www.linkedin.com/company/oktul - YouTube: https://www.youtube.com/@OktulDevelopment - Estonian: https://oktul.com/et/