Install the app in Confluence and connect it to Jira on the same site. One installation covers both, and it runs entirely on Atlassian. Cloud only.

Caution

The Marketplace listing is not live yet. These steps describe the installation flow submitted for Atlassian’s review. The labels will be checked against the listing before launch.

Requirements

Confluence Cloud and Jira Cloud on the same site
Site administrator or Atlassian app administrator permission

Confluence and Jira on different sites will not work.

Install it

Open the Marketplace listing
One application gives both editions. Which one you have follows the subscription.
Select Try it free, at the top right
Evaluation runs through Atlassian rather than through Oktul.
Choose your site, then Install app
Only a site or Atlassian app administrator can install; anyone else sees Request app. It takes up to a minute.
Connect it to Jira
Accept the Jira connection during installation, or later in Atlassian administration. Without it, the macro loads no work items.

Confirm it worked

Edit a page, type /oktul and choose Oktul Work Item Macro. Select the pencil icon. If the list of Jira fields loads, the app works in both products. Next: add the macro to a page.

If it did not work

What you see	What it means
The macro is not in the insert menu	The app is not installed in Confluence on this site, or the installation has not finished. Check Apps, then Manage apps, in Confluence.
Could not load Jira fields when you open the configuration	The app is not connected to Jira. Connect it in Atlassian administration and reopen. Save stays disabled meanwhile.
App not installed in Jira on the page	The same cause. The table returns once Jira is connected.
Cannot reach Jira on the page	Jira answered 401, 403 or 404: the app is not connected, or the reader cannot browse a space the JQL names.
App license is not active on the page	The subscription has lapsed. See below.

Licensing, and what happens when it lapses

Paid per installation through the Marketplace. Standard and Advanced editions; Advanced adds inline editing.

Without an active subscription:

The table and configuration show App license is not active, pointing to Billing in Atlassian administration or Apps > Manage apps.
Exports carry one line in place of the table.
Confluence is untouched.

What a lapsed licence leaves alone

Every macro keeps its configuration and comes back as it was.
Moving to Standard keeps the editing settings, unused until you return to Advanced.

Removing the app

Uninstalling from Confluence also removes it from Jira. Macro configurations stay in the pages; the app keeps no other data. See privacy and data handling.

A problem or a question? Write to support@oktul.com or open a request in the Help Center (opens in a new tab).