DEV Community: Yamuno Software

Script Toolkit for Jira is live on the Marketplace

Yamuno — Thu, 15 Oct 2026 06:44:44 +0000

Script Toolkit for Jira is live on the Marketplace

Short answer: Script Toolkit for Jira is now on the Atlassian Marketplace, and it's free. It lets Jira admins extend Jira Cloud with JavaScript: your own panels on work items, dashboard gadgets, web triggers for other systems, scheduled jobs, scripted fields and workflow validators. Everything runs on Atlassian Forge, inside your Jira site, and backend scripts are read only unless you allow writes.

Most Jira teams have a short list of small things they wish Jira did. Show the linked deployment on every work item. Post a comment when CI finishes. Count overdue work every morning. Refuse a transition when a field is empty. Each one is a few lines of code, but until now each one meant building and hosting a whole app, or living without it. Script Toolkit gives those few lines a place to run.

What you can build

Try code in the Script Console

Open Jira settings → Apps → Script Toolkit → Script Console, write JavaScript, and press ⌘↵ (Ctrl+↵ on Windows). The console runs in your browser with your own Jira permissions and saves nothing, so it's a safe place to explore the Jira REST API before you turn code into a script:

const res = await requestJira('/rest/api/3/search/approximate-count', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ jql: 'statusCategory != Done AND assignee = currentUser()' }),
})
const { count } = await res.json()
return `${count} open work items assigned to you`

await works at the top level, and whatever you return is shown under the editor. The Script Console guide lists every global you can use.

Fragments: your own panels inside Jira

A fragment is HTML, CSS and JavaScript that Script Toolkit shows inside Jira. Put it in a panel on every work item, in a dialog opened from the work item's ••• menu, on a project page or in project settings. Several fragments in the same place appear as tabs.

Fragments run in the viewer's browser and call Jira as the viewer, so people only ever see what they could already see. Use Atlassian design tokens and your panel follows Jira's light and dark themes. The fragments guide has a minimal example you can paste and save.

Dashboard gadgets

Gadget scripts work like fragments, but on a dashboard. Add the Script Toolkit Gadget, pick one of your gadget scripts, and each gadget on the dashboard can show a different one. Each viewer sees their own data. See Gadgets for the setup. If what you need is a standard chart rather than custom code, Charts for Jira Dashboard is the quicker route.

Web triggers for other systems

A web trigger gives a script a secure URL with its own secret. A CI pipeline, a monitoring alert or a form can call it, and whatever the script returns comes back as JSON. Calls without the right secret get a 401 before any script runs, and you can rotate the secret at any time. The web triggers guide shows a full example that comments on a work item when a deploy finishes.

Scheduled jobs

Run a backend script on a cron schedule in UTC: a morning count of overdue work, a weekly clean-up, a nightly sync with another tool. Jobs are checked every five minutes and can run for up to five minutes each. See Scheduled jobs.

Scripted fields

Create a custom field whose value a script computes when the work item is shown: text, number, user, date or date time. For example, the number of done subtasks, or a due date worked out from other fields. Field runs have their own daily limit, so heavy browsing can't use up the budget your jobs and triggers need. See Scripted fields.

Workflow validators and post-functions

Attach a script to a transition. A validator can block it and tell the user why, for example "Assign this work item first." A post-function runs after the transition, to add a comment or set a field. A validator that fails or times out allows the transition, so a broken script can never lock a workflow. See Workflow extensions.

Bulk tools for people who aren't admins

Script Toolkit also includes seven ready-made bulk tools for work items: transition, set resolution, assign, add a comment, edit labels, set priority, and copy one custom field into another. You open each tool to admins, chosen groups or everyone. People run a tool on a JQL query, up to 5,000 work items at a time, and it uses their own Jira permissions, so access to a tool grants no new rights. The tools guide covers access and limits.

Safe by default

Running code inside Jira should not mean giving up control, so the defaults are strict:

Only Jira admins write scripts. Everyone else only sees the results, or runs the bulk tools you open to them.
Backend scripts are read only unless you set a script's Jira access to Read and write. Any request that would change data is refused before it is sent.
Outbound calls happen only if you allow them, either to a list of hosts you choose or to any public https host. Private and internal addresses are always refused.
Secrets stay secret. API keys live in Forge's encrypted secret storage, can't be read back from the UI, and are masked in logs.
Every run has limits: a time limit per run and daily limits per site, which admins can adjust within set ranges.
Every run is logged, grouped by run and filterable by script, with a retention you set.

Backend scripts run in an isolated JavaScript sandbox inside the app, on Atlassian's infrastructure. Yamuno runs no servers for Script Toolkit and receives none of your data. The data and privacy page lists what the app stores and each permission it asks for, and our Forge security checklist explains what "runs on Atlassian" means when you compare apps.

Who it's for

Jira admins who keep getting asked for "just one small panel" or "one more rule on this transition"
Platform and DevOps teams connecting CI, deploys and monitoring to Jira through web triggers
Team leads and support staff who need bulk changes without becoming Jira admins
Anyone reporting from Jira who wants a computed field or a scheduled count instead of a manual spreadsheet; our guide to Jira reporting for product managers covers where those numbers fit

If you also need to see what changed on work items and how long they sat in each status, Issue History+ for Jira works well alongside it.

Getting started

Install Script Toolkit for Jira from the Atlassian Marketplace.
Open Jira settings → Apps → Script Toolkit → Script Console and click Run on the starter script.
Open Scripts, choose Fragment, test it against a work item key in the Test tab, and save it.
Open that work item and find your fragment in the Script Toolkit panel.
Create a Web trigger and call it with the example command under How to call it.

The quick start walks through all of this in about fifteen minutes.

Frequently asked questions

How much does Script Toolkit cost?

It's free on the Atlassian Marketplace.

Which language are scripts written in?

JavaScript. Fragments and gadgets are HTML with JavaScript that runs in the viewer's browser. Backend scripts are modern JavaScript with top-level await, run in an isolated sandbox inside the app. There is no Node.js, so no require or file system.

Who can write scripts?

Only Jira admins. Fragments and gadgets then run for everyone who views them, with each viewer's own permissions, and bulk tools can be opened to chosen groups.

Do scripts run on external servers?

No. Everything runs on Atlassian Forge, inside your Jira site. Yamuno runs no servers for the app.

Can a backend script change Jira?

Only if you allow it. Each backend script is read only by default; set its Jira access to Read and write when it needs to create or change data.

Can I test a script before it goes live?

Yes. The editor's Test tab runs the unsaved code once, against a work item key or a request body, and fragments and gadgets can be previewed under the editor before you save.

Try it

Install Script Toolkit for Jira and run your first script in the console. Questions or feedback? Reach us through our support portal. Your input shapes what we build next.

Issue History+ for Jira is live on the Marketplace

Yamuno — Tue, 13 Oct 2026 16:43:42 +0000

Issue History+ for Jira is live on the Marketplace

Short answer: Issue History+ for Jira is now on the Atlassian Marketplace, and it's free. It reads the change history Jira already records and lets you search it for a whole project, sprint or JQL query, see how long work spends in each status, and find stuck work, rework and SLA breaches. It runs on Atlassian Forge, so your issue data never leaves Atlassian.

Jira writes down every change to every issue: who moved it, who reassigned it, who rewrote the description, and when. Reading that record is the hard part. The History tab shows one issue at a time, so answering "who moved these tickets back to In Progress last week?" means opening them one by one. We built Issue History+ to answer that kind of question in one search.

What the app does

Search the change history of many issues at once

Open Apps → Issue History, pick a project and a date range, and click Search. You get every field change for the matching issues in one table. There are three ways to choose the issues:

Standard: project, sprint, issue type, assignee, reporter, label, group and date range
JQL: paste a query you already use, with autocomplete and validation
Bulk: a list of issue keys, for example from a release note

Group the results by issue, project, author or field, or read them as a feed. Summary and description edits show word-level differences, so you can see exactly which words changed instead of comparing two long paragraphs. Highlight marks every change one person made. The searching history guide covers each option.

Time in status

The Time in Status tab shows, for each status, the median time per visit and the time 85% of visits finish within. We chose those over averages on purpose: one issue forgotten in review for three months can drag an average far from what a typical issue experiences, while the median and the 85th percentile stay honest.

Time runs from the moment an issue enters a status until it leaves, and repeat visits are added up. You can count calendar time or business hours, and set an SLA per status so breaching issues are marked. A per-issue table lets you sort by any status to find the issues that spent longest there. The time in status guide explains how each number is calculated.

Status timeline

The Status Timeline tab draws each issue's path through your workflow as one bar, coloured by status category. It makes ping-pong between In Progress and In Review easy to spot, which is hard to see in a list of changes.

Insights

Insights summarises the current search:

Completed and in-progress issues
Median cycle time and the cycle time 85% of issues finish within
Reopened issues: anything that left Done at least once
Inactive work: issues that are not done and have had no status change for 7, 14 or 30 days
Rework: the share of status moves that go backwards
SLA breaches, worst first

It also shows issues completed per week, the most common status changes, when changes happen during the week, and who changes what. Every metric is defined in the Insights guide.

Because the app uses each status's Jira category (To Do, In Progress, Done), custom statuses such as Shipped or Won't Fix count correctly without any setup.

Issue Insights on every issue

Each issue gets an Issue Insights tab in its Activity section. It shows that issue's total time in each status, its status timeline and every change, newest first. You don't need to leave the issue to see where it has been.

Restore

For status, assignee, priority and summary, Restore puts the field back to the value it had before a change. It uses Jira's normal edit and transition permissions, so it only works where you could make that change in Jira yourself.

Reports for people outside Jira

Export the current search to CSV, Excel or a PDF report with your company name and logo. Excel and PDF exports include SLA thresholds and how many issues went over them. You can also save a search as a private bookmark, and your last ten searches are one click away.

Your data stays in Atlassian

Issue History+ runs entirely on Atlassian Forge and declares no egress, so issue data is never sent to an external server. Every request runs as the signed-in user, which means people only see history for issues they can already browse in Jira.

The app stores only each user's saved searches, recent searches, settings and PDF branding, in Forge storage for your site. It doesn't store issue data, names or email addresses. The data and privacy page lists everything it reads and stores, along with each permission it asks for. If you are comparing apps on this point, our Forge security checklist explains what "runs on Atlassian" means in practice.

Who it's for

Scrum masters and team leads who want to see where work waits and which issues have gone quiet, before stand-up
Jira admins answering "who changed this field, and when?" for many issues at once
Support and service teams tracking time in each status against an SLA
Product and delivery managers who need cycle time and throughput without building a spreadsheet; our guide to Jira reporting for product managers shows where it fits alongside Jira's own reports
Anyone reporting to stakeholders who don't use Jira, through PDF and Excel exports

For a walkthrough of a full setup, from measuring time in status to setting SLAs, see the time in status and issue history use case. If you also want charts on your Jira dashboard, Charts for Jira Dashboard works well next to it.

Getting started

Install Issue History+ for Jira from the Atlassian Marketplace.
Open Apps → Issue History, choose a project and keep the default last 30 days.
Click Search, then open the Time in Status and Insights tabs.
Open any issue and choose Issue Insights under Activity.
Click Export to share a report.

The quick start takes about ten minutes.

Frequently asked questions

How much does Issue History+ cost?

It's free on the Atlassian Marketplace.

Where does the history come from?

From Jira's own changelog, read through the Jira REST API as the signed-in user. The app fetches the complete history of each issue, not only the most recent changes.

Can people see history for issues they can't access?

No. Every request runs with the viewing user's Jira permissions, so people only see history for issues they can already browse.

Does it work with company-managed and team-managed projects?

Yes. Both project types record the standard Jira changelog, which is what the app reads.

Does it change anything in Jira?

Only when someone clicks Restore, and only for status, assignee, priority or summary. Everything else is read only.

Try it

Install Issue History+ for Jira and run your first search. Questions or feedback? Reach us through our support portal. Your input shapes what we build next.

PDF Exporter adds scheduled exports and a REST API

Yamuno — Tue, 13 Oct 2026 07:58:10 +0000

PDF Exporter adds scheduled exports and a REST API

Short answer: the 13 October 2026 release of PDF Exporter for Confluence is the biggest since launch. Large exports now run on Atlassian's servers in the background, so you can close the page while they finish. Schedules export a space or page tree every week or month and attach a dated PDF to an archive page. And a REST API lets scripts and CI/CD pipelines start exports with an API token.

Until now, every export was built in your browser. That works well for a handful of pages, but a 400-page space export meant keeping a tab open, and a monthly compliance snapshot meant someone remembering to click Export on the first of the month. This release is about taking both of those jobs off people's hands.

Background exports and My exports

The exporter's sidebar has a new Where to generate option:

Auto (recommended): small exports are built in your browser, large ones go to the server. The exporter tells you which it picked and why.
This browser: always build locally. Fastest for a few pages, but the page has to stay open.
Server (background): always build on the server, and leave whenever you like.

With Auto, an export moves to the server when it has more than 30 pages, more than 60 attachments, or more than 50 MB of attachments.

A progress card shows each step (fetching pages, rendering, laying out the PDF). When it's done you can download from the card, or find the file later under My exports in the sidebar. If you close the exporter mid-export, the card comes back the next time you open it.

My exports keeps your server exports for 7 days by default. Large ZIP exports come in parts, download links are created when you click, and exports attached to a page have an Open on page link. Site admins set the retention period (1 to 90 days) and a storage limit for the site under Confluence Settings → PDF Exporter → Exports & storage.

Background exports run on Atlassian Forge and the files sit in Atlassian's own storage. Nothing leaves Atlassian. The background exports docs cover the details.

Scheduled exports

Schedules are for teams that keep audit or retention copies of their documentation, or anyone who needs a monthly "as it was" copy.

Open Apps → PDF Exporter for Confluence, choose Schedules in the sidebar and click New schedule. A schedule has:

What to export: a page and its children, or a whole space
Style Template: any saved template; template edits apply to the next run
Output: one merged PDF or a ZIP of PDFs
How often: weekly on a weekday, or monthly on a date from 1 to 28
Where it goes: attached to an archive page you choose, or kept in My exports only
Notify by email: every run, only failures, or off

When a run attaches its file to an archive page, the file is named with the schedule name and the run date, for example Compliance snapshot 2026-11-01.pdf. The page's attachments then list every run in order, and those files stay until someone deletes them.

Email notifications without noise

Notifications use Confluence itself. After a run, the app comments on the archive page and @mentions the people you picked, and Confluence emails them as it does for any mention. Each schedule keeps one comment thread and adds every later run as a reply, so a weekly schedule doesn't bury the page in comments after a year. Only failures keeps the thread quiet unless something goes wrong.

Failures you can act on

A failed run shows its reason in plain words, such as "Archive page was deleted". Problems that can't fix themselves (a deleted archive page, a deleted space, an owner who left) pause the schedule straight away. Other failures pause it after three in a row. Run now runs a schedule immediately without moving its regular dates, which is handy for a first test. Site admins see every schedule on the site, with its owner, status and next run.

Each run uses the access of the person who created the schedule, so it only exports pages they can view. The scheduled exports docs list every option. For the bigger picture on audit copies, see Confluence PDF export for compliance teams.

A REST API for scripts and pipelines

Some exports belong to a process rather than a person: release notes at the end of a deployment, a spec frozen when a project closes, a nightly copy of a runbook space. The new REST API covers those.

A site admin creates a token under Confluence Settings → PDF Exporter → API, choosing an expiry of 30 days, 90 days, 180 days or 1 year. Then one request starts an export:

curl -X POST 'YOUR_ENDPOINT_URL' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"pageId": "123456", "name": "Release notes"}'

A 202 response means the export started. The request can export a page, a page tree or a space, use any saved template, attach the file to a page and @mention up to 10 people. Send a requestId and a retried request starts nothing new. Each token has a Recent calls log of its last 25 requests, and only a hash of the token is stored.

One design choice is worth knowing about. API responses are fixed messages and carry no page data, and no data is sent out of Atlassian. That keeps PDF Exporter eligible for Atlassian's Runs on Atlassian program. It also means the response tells you the export started, not where the file is: you pick it up in My exports, on the page you attached it to, or from the mention email. The REST API guide and examples show common jobs.

If you already automate Confluence content, the same token-based approach is used by the Markdown Importer REST API.

Fair use: one server export at a time

Server exports run one at a time per site, and that includes scheduled runs and API calls. When another export is running, yours shows Waiting in Line with its place in the queue and a Cancel button, and starts on its own.

Each site can render 10,000 pages a month on the server. Browser exports don't count toward that, and the allowance resets on the first of each month (UTC). Admins see this month's usage under Server exports this month.

Because server exports need new permissions, sites on an older version see a notice that an update is waiting, with a link to Manage apps for admins.

Smaller changes and fixes

The exporter and the settings page now use a sidebar, and remember the open section in the page address
Clicking Export shows Preparing Export straight away, and the button can't be clicked twice
Custom emoji keep their image, panels keep their background colour and decision items keep their formatting
Table of contents zone macros are no longer left out
Long code lines without spaces wrap instead of running off the page
Embeds without a source show a named "not included" note

The full list is in the release notes.

Frequently asked questions

Do I need to do anything to get the new features?

A site admin needs to approve the update in Manage apps, because server exports use new permissions. Until then the exporter shows a notice with a link.

Do small exports still happen in my browser?

Yes. With Where to generate set to Auto, exports of up to 30 pages (and within the attachment limits) are still built in your browser and download straight away. You can also force either option.

How long are background exports kept?

Seven days by default. Admins can set anything from 1 to 90 days, plus a storage limit for the site. Files that a schedule or API call attached to a Confluence page stay on that page until someone deletes them.

Can a scheduled export run at a set time of day?

No. Schedules run once on their day, and Confluence picks the time. Dates are in UTC, so a schedule says "every Monday", not "every Monday at 9:00".

What can the REST API export?

A single page, a page tree or a whole space, with any saved template, as one merged PDF (up to 500 pages) or a ZIP of separate PDFs (up to 2,000 pages). Each token can start 30 exports an hour.

Does any of this send data outside Atlassian?

No. Background and scheduled exports run on Atlassian Forge and store files in Atlassian's storage, and API responses carry no page data.

Try it

Install PDF Exporter for Confluence from the Atlassian Marketplace, or update it under Manage apps if you already have it. New to the app? Start with how to export Confluence to PDF or the getting started guide.

Questions or feedback? Reach out via our support portal.

Confluence Markup: Wiki Markup vs Markdown in Cloud

Yamuno — Tue, 13 Oct 2026 07:57:58 +0000

Confluence Markup: Wiki Markup vs Markdown in Cloud

Short answer: Confluence markup, also called Confluence wiki markup or the Confluence markup language, is Atlassian's own text syntax (h1., *bold*, {code}), and Markdown is the syntax most developers write everywhere else (#, **bold**, triple backticks). The Confluence Cloud editor no longer accepts wiki markup, but it does turn common Markdown shortcuts into formatting as you type. If you want to keep Markdown as the source of a page, you need a Markdown macro or an importer.

If you have been using Confluence for a while, you probably learned wiki markup first. If you came from GitHub, GitLab or a docs-as-code setup, you think in Markdown. Both describe the same things, headings, lists, tables, code, but the symbols are different, and only one of them still has a place in the Cloud editor. This guide puts the two side by side and explains what to use today.

What is Confluence markup?

Confluence markup is the plain-text format the original Confluence editor was built around. Atlassian calls it wiki markup, and Jira Data Center and Jira's version 2 REST API use the same syntax. Before the rich text editor took over, you wrote pages as text with markup and Confluence rendered them. A heading was h2. Release notes, a table header row was ||Name||Owner||, and a code sample sat between {code} tags.

That syntax still exists in a few places:

Confluence Data Center still documents and supports wiki markup.
The legacy Confluence Cloud editor has an Insert > Markup dialog that accepts wiki markup or Markdown and converts it into rich text.
Older pages and scripts. Content written years ago, and tools built on Jira's version 2 REST API, which takes rich text fields as wiki markup, still use it.

In the current Confluence Cloud editor, Atlassian states plainly that markup insertion is not supported. You cannot open a page and edit its wiki markup source either; the page is stored in Confluence's own format and you work on it as rich text.

Markdown in the Confluence Cloud editor

What the Cloud editor does have is autoformatting that follows Markdown conventions. Type these and Confluence converts them on the spot:

# followed by a space for Heading 1, up to ###### for Heading 6
**bold**, *italic* and ~~strikethrough~~
`code` for inline code, and three backticks followed by a space for a code block
* followed by a space for a bulleted list, 1. followed by a space for a numbered list
[] followed by a space for an action item (a task)
> followed by a space for a quote, and --- followed by a space for a divider
[link text](https://example.com) for a link

This is handy when you write a page by hand. The catch is that it is a typing shortcut, not a Markdown mode. Once the text is formatted, the Markdown is gone. You cannot switch the page back to its Markdown source, and there is no table shortcut, so tables still come from the toolbar or the slash command. For more on code specifically, see inline code and code blocks in Confluence.

Wiki markup vs Markdown, side by side

Here is how the same formatting is written in each syntax.

What you want	Confluence wiki markup	Markdown
Heading 2	`h2. Title`	`## Title`
Bold	`bold`	`bold`
Italic	`_italic_`	`italic`
Strikethrough	`-deleted-`	`~~deleted~~`
Inline code	`{{code}}`	`code`
Code block	`{code:java}` … `{code}`	three backticks plus the language, then three backticks
Bulleted list	`* item`	`- item` or `* item`
Numbered list	`# item`	`1. item`
Link	`[title\	https://example.com]`{% endraw %}
Table header	{% raw %}`\	\
Quote	{% raw %}`bq. text`	`> text`
Horizontal rule	`----`	`---`

Three differences catch people out:

Asterisks mean different things. In wiki markup *text* is bold; in Markdown it is italic. Paste one into the other and the emphasis changes.
# is a numbered list in wiki markup and a heading in Markdown. A wiki-style numbered list pasted into a Markdown file turns into a stack of headings.
Links put the title and URL in a different order and with a different separator. Wiki markup uses [title|url], Markdown uses [title](url).

Confluence wiki markup cheat sheet

Wiki markup also covers things standard Markdown has no syntax for, such as coloured text, panels and user mentions. These are the ones you are most likely to meet in older pages and Jira issue descriptions.

What you want	Confluence wiki markup
Underline	`+underlined+`
Superscript and subscript	`^super^` and `~sub~`
Coloured text	`{color:red}text{color}`
Line break	`\\`
Image from an attachment	`!diagram.png!`, or `!diagram.png\
Link to an attachment	{% raw %}`[^report.pdf]`
Link to another page	`[Page title]` or `[SPACEKEY:Page title]`
Mention a user	`[~username]`
Anchor and link to it	`{anchor:setup}` and `[#setup]`
Table cell	`\
Info, note, tip, warning panels	{% raw %}`{info}text{info}`, `{note}`, `{tip}`, `{warning}`
Panel with a title	`{panel:title=Before you start}text{panel}`
Preformatted text, no highlighting	`{noformat}text{noformat}`
Multi-line quote	`{quote}text{quote}`
Table of contents	`{toc}`

Anything in curly braces is a macro, which is why {code}, {info} and {toc} look alike. Standard Markdown has no equivalent for most of them. In the Cloud editor you add the same things from the slash menu instead: type /info for an Info panel or /table of contents for a table of contents.

Which one should you use?

For new content, Markdown. It is what developers already write in READMEs, pull requests, chat and issue trackers, it is supported by almost every docs tool, and the Confluence Cloud editor's shortcuts follow it.

Wiki markup still makes sense in two situations: you run Confluence Data Center and your team already knows it, or you maintain scripts that write to Jira's version 2 API. Outside of those, learning wiki markup today mostly means learning a syntax that only Atlassian products read.

Converting between the two

There is no built-in converter in Confluence Cloud, so most teams handle it one of three ways:

By hand, for a few pages. The table above covers nearly everything. Watch the three traps: asterisks, # and link order.
Export existing pages to Markdown. If the content already lives in Confluence, export it rather than converting text. Markdown Exporter for Confluence exports a page, a page tree or a whole space to Markdown files with front matter. See how to export Confluence to Markdown.
Import Markdown into pages. Going the other way, Markdown Importer for Confluence turns .md files, folders or a ZIP into a Confluence page tree. The walkthrough is in how to import Markdown into Confluence.

Search-and-replace scripts between the two syntaxes look easy and rarely are. Nested lists, code blocks that contain asterisks, and tables with links all break simple patterns, so test a converted page before you trust a batch.

Keeping Markdown as Markdown in Confluence

The editor's shortcuts and the Insert > Markup dialog both convert Markdown into rich text. That is fine for a one-off page. It is a problem when the Markdown is the real source, a README, an API reference or a runbook that also lives in Git, because the next edit has to be made twice.

Two ways keep the Markdown intact:

Write Markdown inside the page. Markdown Macro+ for Confluence adds a macro with a split editor and live preview. You write GitHub-flavoured Markdown, including tables, task lists, code with syntax highlighting and KaTeX math, and the source stays editable afterwards. The quick start takes a couple of minutes, and how to write Markdown in Confluence covers it in depth.
Publish from your repository. Keep the .md files in Git and push them to Confluence with Markdown Importer, by hand or from CI. This is the docs-as-code setup described on the technical documentation use case page.

Both apps are built on Atlassian Forge, so the content stays on your Atlassian site.

Frequently asked questions

What is the Confluence markup language?

It is Confluence wiki markup, the plain-text syntax Atlassian created for Confluence and Jira. Headings are h1. to h6., bold is *text*, code blocks sit between {code} tags and macros are written in curly braces. The current Confluence Cloud editor no longer accepts it; Data Center and the legacy Cloud editor do.

Does Confluence Cloud still support wiki markup?

Not in the current editor. Atlassian's documentation says the new editor does not support markup insertion, and pages are not editable as wiki markup. The Insert > Markup dialog only exists in the legacy editor, and Confluence Data Center still supports wiki markup.

Can I write Markdown in Confluence Cloud?

You can type Markdown shortcuts such as ##, **bold** and three backticks, and the editor formats them as you type. The Markdown itself is not kept. To keep editable Markdown on a page, use a Markdown macro such as Markdown Macro+.

What is the difference between Confluence markup and Markdown?

They describe the same formatting with different symbols. The biggest differences: *text* is bold in wiki markup and italic in Markdown, # starts a numbered list in wiki markup and a heading in Markdown, and links are [title|url] versus [title](url).

How do I convert Confluence wiki markup to Markdown?

For a few pages, convert by hand with a reference table like the one above. For content that is already in Confluence, export the pages to Markdown instead of converting text, for example with Markdown Exporter for Confluence.

Can I paste a README into Confluence and keep its formatting?

Pasting raw Markdown into the Cloud editor does not reliably keep its formatting. Put it in a Markdown Macro+ macro on the page, or import the file with Markdown Importer so headings, tables and code blocks come through.

Try it

Write your next README-style page in Markdown and keep it that way: install Markdown Macro+ for Confluence from the Atlassian Marketplace, add the macro to a page and paste your Markdown in. If the docs live in Git, try Markdown Importer on one folder first.

LaTeX Inline Math: $...$, \$...\$ and Display Math

Yamuno — Thu, 08 Oct 2026 15:20:12 +0000

LaTeX Inline Math

Inline math is an equation that sits inside a sentence, like "the roots are x = ±2" or "the loss is O(n log n)". LaTeX has two ways to write it, and a separate mode for equations that should stand on their own line. This guide covers both, what changes when math is inline, and how inline equations work outside a LaTeX document, in Markdown, Jupyter and Confluence.

Short answer:

Inline math: wrap the expression in single dollar signs, $E = mc^2$ , or in $E = mc^2$.
Display math (its own centered line): use \[E = mc^2\]. Avoid $$...$$ in LaTeX documents.

$...$ or $...$?

Both produce exactly the same inline equation:

The area of a circle is $A = \pi r^2$.
The area of a circle is \(A = \pi r^2\).

$...$ is shorter and is what almost everyone types. $...$ is the LaTeX form: the opening and closing delimiters are different, so a missing one gives a clear error instead of silently swapping text and math for the rest of the paragraph. Pick one and use it consistently in a document.

To print a literal dollar sign in text, escape it: \$5.

Display math: \[...\], not $$...$$

When an equation needs its own line, use display math:

The solutions are
\[
  x = \frac{-b \pm \sqrt{b^2 - 4ac}}{2a}
\]
for any quadratic with a ≠ 0.

$$...$$ also produces display math, but it is plain TeX syntax. In a LaTeX document it can give inconsistent spacing above and below the equation and doesn't work with the fleqn option, so \[...\] (or an environment such as equation or align from amsmath) is the recommended form. Many Markdown renderers and web tools do accept $$...$$, which is why you see it so often online.

What changes when math is inline

LaTeX shrinks inline math so it doesn't push the lines of the paragraph apart:

Sums, products and limits put their limits to the side instead of above and below. $\sum_{i=1}^{n} x_i$ shows the i = 1 and n next to the sigma, not over and under it.
Fractions are set smaller, with the numerator and denominator in a smaller font.
Big operators such as integrals are smaller.

That is usually what you want. When it isn't, you can override it:

Goal	Write
Limits above and below a sum, inline	$\sum\limits_{i=1}^{n} x_i$
A full-size fraction inline	$\dfrac{a}{b}$ (amsmath)
A small fraction in display math	`\[\tfrac{1}{2}\]` (amsmath)
Display-size everything in one inline expression	$\displaystyle \sum_{i=1}^{n} \frac{1}{i}$

Use these sparingly. A tall inline expression forces extra space between lines, and the paragraph looks uneven. If an inline equation needs \displaystyle to be readable, it probably belongs on its own line.

Text and spacing inside inline math

Inside math, letters are variables and spaces are ignored. So:

Words need \text{}: $x > 0 \text{ for all } x \in S$ . Without it, "for all" prints as six italic variables with no spaces.
Function names need their commands: $\log n$ , $\sin x$ , $\max(a, b)$ . See log and ln in LaTeX.
Add space by hand when needed: \, (thin), \; (thick), \quad (wide).
Keep punctuation outside the math when it belongs to the sentence: $x = 2$. rather than $x = 2.$ .

Inline math in Markdown, GitHub and Jupyter

Most Markdown tools that support math use the same delimiters:

GitHub renders $...$ inline and $$...$$ as a block in Markdown files, issues and pull requests. If a dollar sign gets misread, GitHub also accepts the form with backticks inside the dollars, a dollar sign then a backtick before the math and a backtick then a dollar sign after it.
Jupyter notebooks render $...$ and $$...$$ in Markdown cells with MathJax.
Static site generators and docs tools usually need a math plugin (KaTeX or MathJax) enabled before $...$ renders at all.

Because $ also means money, some renderers only treat $...$ as math when there is no space just inside the dollar signs. $x$ works; $ x $ may not.

Inline math in Confluence

Confluence Cloud has no built-in math, so you need an app. With LaTeX Math for Confluence, type /latex in the editor and choose LaTeX Math (Inline) for an equation inside a sentence or LaTeX Math (Block) for display math.

Delimiters are optional in both macros. The inline macro accepts E = mc^2, $E = mc^2$ or $E = mc^2$, so you can paste LaTeX from a paper or a Markdown file as it is. If you paste display delimiters such as $$...$$ or \[...\] into the inline macro, they are converted to inline math. Multi-line environments and large matrices belong in the block macro.

The app renders with KaTeX, so the commands in our LaTeX symbols reference that are marked as KaTeX-supported all work. For a full walkthrough, see how to add math equations to Confluence.

Common mistakes

Problem	Cause	Fix
The rest of the paragraph turns italic	A missing closing `$`	Close the math, or switch to `$...$` so the error is reported
Words inside an equation run together	Text typed in math mode	Wrap words in `\text{}`
An inline fraction looks tiny	Inline style is applied	Use `\dfrac` once, or move the equation to display math
Lines in the paragraph spread apart	A tall inline expression	Put the equation on its own line with `\[...\]`
A price prints as math	`$` read as a delimiter	Escape it as `\$`

FAQ

What is the difference between $ and $$ in LaTeX?
Single dollars give inline math inside a sentence. Double dollars give display math on its own line, but in LaTeX documents \[...\] is preferred.

How do I write inline math in LaTeX without dollar signs?
Use $ and $. They behave exactly like $...$ .

How do I make a sum show its limits above and below inline?
Add \limits: $\sum\limits_{i=1}^{n}$ . Or set the whole expression in display style with \displaystyle.

Can I use inline math in a heading?
Yes in LaTeX, but use it sparingly, because the math also appears in the table of contents and in PDF bookmarks, where it may not render. In Confluence, put the equation in the body text instead.

Confluence Inline Code & Code Blocks (Complete Guide)

Yamuno — Tue, 06 Oct 2026 16:59:01 +0000

Inline Code and Code Blocks in Confluence

If you write anything technical in Confluence, you need two things: a way to mark a command or file name as code in the middle of a sentence, and a proper block for anything longer than one line. Confluence Cloud has both, but the options for inline code and code blocks are spread over a toolbar menu, a few shortcuts and some Markdown that only works when you type it.

Short answer:

Inline code: type text between two backticks, like `npm install`, or select text and press Ctrl+Shift+M (Cmd+Shift+M on a Mac).
Code block: type three backticks (```) at the start of a line, or type /code and pick Code snippet.

The rest of this guide covers every way to add each one, the settings a Confluence code block has, what changed from the old Code Block macro, and how to fix the things that usually go wrong.

When to use inline code vs a code block

Use inline code in Confluence for short things that sit inside a sentence: a command, a function name, a file path, a config key, an error message. For example: "Set retryCount to 3 in config.yaml."

Use a code block for anything you'd copy and run, anything longer than a line, and anything where indentation matters. Code blocks keep whitespace, get syntax highlighting and have a copy button, so readers don't pick up stray characters from the page.

A simple rule we use: if someone will paste it into a terminal or editor, it goes in a block.

How to add inline code in Confluence

There are three ways to add Confluence inline code formatting. They all produce the same result, so pick whichever fits how you type.

Type backticks

Type a backtick, your text, and a closing backtick: `kubectl get pods`. Confluence converts it to inline code the moment you type the closing backtick. This is the fastest way if you already write Markdown elsewhere.

It only works when you type it. If you paste text that already contains backticks, they stay as plain characters. In that case use the shortcut below.

Use the keyboard shortcut

Select the text and press:

	Shortcut
Windows / Linux	Ctrl + Shift + M
Mac	Cmd + Shift + M

Press the same shortcut again to remove the formatting.

Use the toolbar

Select the text, open the Format text menu in the editor toolbar (the ... next to bold and italic) and choose Code.

To stop typing in code format, press the right arrow key at the end of the inline code, or toggle the shortcut off.

How to add a code block in Confluence

There are four ways to insert a code block. Atlassian's editor calls it a code snippet, so that's the name you'll see in menus.

Three backticks. On an empty line, type ``` and a code block appears. You can type the language right after the backticks, like ```python, before pressing Enter.
Slash command. Type /code and choose Code snippet from the list.
Insert menu. Click + in the toolbar and choose Code snippet.
Convert existing text. Paste your code, select it, and use one of the methods above. For multi-line code it's usually cleaner to insert the empty block first and paste into it, so the indentation stays intact.

Code blocks work in pages, live docs, templates and inside most other elements, including table cells and expand sections.

Confluence code block options

Click inside a code block and a small toolbar appears with its settings.

Language and syntax highlighting

New code blocks detect the language automatically for CSS, Go, HTML, Java, JavaScript, JSON, Python, Ruby, Rust, Shell, SQL and TypeScript. For anything else, or when detection guesses wrong, pick the language from the dropdown. Once you choose one manually, auto-detection is switched off for that block.

Setting the language explicitly is worth the extra second. It gives correct highlighting, and readers can see at a glance whether a snippet is Bash or PowerShell.

Line numbers

Line numbers are on by default. Select the block and choose Hide line numbers to turn them off, which is handy for one-line commands. Choose Show line numbers to bring them back.

Wrapping long lines

Long lines scroll sideways by default. Select Wrap code to wrap them instead, or Unwrap code to go back. The setting you choose while editing is saved with the page. When a reader toggles wrapping in view mode, it only changes their view.

Formatting code

For JavaScript and JSX, JSON and SQL, Confluence can tidy spacing and indentation for you. This is useful for minified JSON from an API response or a long one-line SQL query.

What changed from the old Code Block macro

If you've used Confluence Server, Data Center or the legacy Cloud editor, you'll remember the Code Block macro. It had a few settings the new code snippet doesn't:

Old Code Block macro	New code snippet	Workaround
Title shown in a header row	No title	Put a short heading or bold line above the block
Collapsible	Not collapsible	Wrap the block in an Expand element (`/expand`)
First line number setting	Always starts at 1	Add a note above the block, or use a comment for context
Themes (Midnight, Eclipse, RDark and others)	Follows the Confluence theme, including dark mode	Use an app if you need a custom look
Language picked by hand	Auto-detect plus manual picker	None needed

Collapsible code snippets are an open feature request with Atlassian (CONFCLOUD-71495), so the Expand element is the practical answer for now. Atlassian is also retiring the legacy editor, so old pages will move to the new code snippet over time.

Common problems and how to fix them

Problem	Why it happens	Fix
Backticks stay as text	The shortcut only converts text as you type it, not pasted text	Select the text and press Ctrl/Cmd+Shift+M
Indentation is lost after pasting	Code was pasted into a normal paragraph first	Insert an empty code block, then paste into it
Wrong colours in the block	Auto-detect guessed the wrong language	Pick the language from the dropdown
Readers scroll sideways forever	Long lines with wrapping off	Turn on Wrap code, or break lines in the code itself
Can't type normal text after inline code	Cursor is still inside the code formatting	Press the right arrow key, or toggle the shortcut off
Page is a wall of code	Whole files pasted into one block	Split into short blocks with a sentence before each one

Writing code in Markdown inside Confluence

Some teams would rather write docs in Markdown and keep the same files in Git. Confluence's editor accepts Markdown shortcuts while you type, but it doesn't store or render a Markdown document as a whole. If you paste a README full of fenced code blocks, it won't come out as you expect. We cover the options in more detail in how to write Markdown in Confluence.

If that's your workflow, Markdown Renderer for Confluence renders GitHub-flavoured Markdown inside a macro, including fenced code blocks with syntax highlighting and inline code in single backticks:

## Install

Run `npm install` first, then start the server:

```bash
npm run dev -- --port 3000
```

The source stays as plain Markdown, so you can copy it between Confluence, GitHub and your editor without reformatting. For fully custom styling, such as a branded code block or a tabbed example, you can also build it yourself with HTML Macro+ for Confluence.

Tips for readable code in Confluence

Keep blocks short. One block per step reads better than one block for the whole procedure.
Explain before you show. Add a sentence above each block saying what it does and where to run it.
Always set the language when auto-detect isn't sure. It's the quickest readability win.
Use inline code for names, not emphasis. If it isn't something you'd type, it doesn't need code formatting.
Never paste secrets. API keys and passwords in code blocks end up in page history, exports and search.
Mark placeholders clearly, for example <your-api-key>, so nobody runs a command with a dummy value.

For bigger documentation projects, see our guides on documenting APIs in Confluence and using Confluence as a developer wiki.

Frequently asked questions

How do I format inline code in Confluence?

Type the text between backticks, like `this`, or select it and press Ctrl+Shift+M (Cmd+Shift+M on a Mac). You can also choose Code from the Format text menu in the toolbar.

What is the keyboard shortcut for inline code in Confluence?

Ctrl+Shift+M on Windows and Linux, Cmd+Shift+M on a Mac. Press it again to remove the formatting.

How do I insert a code block in Confluence?

Type three backticks on an empty line, or type /code and choose Code snippet. You can also click + in the toolbar and pick Code snippet.

Can I make a Confluence code block collapsible?

Not directly. The new code snippet has no collapse option. Put the code block inside an Expand element instead, so readers click to open it.

Can I hide line numbers in a Confluence code block?

Yes. Select the code block and choose Hide line numbers from its toolbar.

Do these shortcuts work in Jira?

Jira Cloud uses the same editor for descriptions and comments, so backticks, three backticks and /code work there too.

Wrapping up

For Confluence inline code, type backticks or press Ctrl/Cmd+Shift+M. For a code block, type three backticks or /code, set the language, and decide on line numbers and wrapping. If your team lives in Markdown, render it with a Markdown macro instead of fighting the editor.

Have a Confluence formatting question we didn't cover? Ask us through our support portal.

5 Ways to Use HTML in Confluence Cloud (With Examples)

Yamuno — Fri, 25 Sep 2026 07:33:16 +0000

5 Ways to Use HTML in Confluence Cloud (With Examples)

Short answer: Confluence Cloud doesn't include an HTML macro. The one you may remember from Server and Data Center was never brought to Cloud, and even on Data Center it's disabled by default. In Cloud you have two options:

The built-in iFrame macro embeds another web page by URL. It can't run your own HTML, CSS or JavaScript, and many sites refuse to be embedded.
An HTML macro app from the Atlassian Marketplace adds a macro where you write your own code. It runs in a sandboxed frame, so it can't affect the rest of the page.

This guide uses HTML Macro+ for Confluence, which is free and runs on Atlassian Forge, but the ideas apply to any HTML macro. The code examples are split into HTML, CSS and JavaScript, matching the editor's three tabs.

What you want to do	Native Confluence Cloud	With an HTML macro
Style a section beyond the built-in panels	Limited to panels, colors and layouts	Any CSS inside the macro
Embed a video, map or design file	iFrame macro, if the site allows embedding	Your own iframe, wrapped in your own layout
Show an existing `.html` file	Attach it as a download	Render it on the page
Add interactive elements	Not possible	Any JavaScript, in a sandbox
Keep migrated Data Center HTML pages working	Shows "unknown macro"	Pages keep rendering

1. Style a section with custom CSS

When you need it: a landing page for your space, a styled call-out, a grid of link cards, or brand colors that the built-in panels don't offer.

One thing to know first: CSS in an HTML macro styles what is inside the macro, not the whole Confluence page. That's by design, because the macro renders in its own sandboxed frame. It means your styles can't break the Confluence UI, and Confluence's styles can't break yours.

HTML

<div class="cards">
  <a class="card" href="/wiki/spaces/ENG/pages/onboarding">
    <span class="card-kicker">Start here</span>
    <h3>Engineering onboarding</h3>
    <p>Accounts, tools and your first week.</p>
  </a>
  <a class="card" href="/wiki/spaces/ENG/pages/runbooks">
    <span class="card-kicker">On call</span>
    <h3>Runbooks</h3>
    <p>Step-by-step fixes for common incidents.</p>
  </a>
  <a class="card" href="/wiki/spaces/ENG/pages/architecture">
    <span class="card-kicker">Reference</span>
    <h3>Architecture</h3>
    <p>How our services fit together.</p>
  </a>
</div>

CSS

.cards {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
  gap: 16px;
  font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
}
.card {
  display: block;
  padding: 20px;
  border: 1px solid #dfe1e6;
  border-radius: 10px;
  color: #172b4d;
  text-decoration: none;
  transition: border-color 0.15s, box-shadow 0.15s;
}
.card:hover {
  border-color: #0c66e4;
  box-shadow: 0 4px 12px rgba(9, 30, 66, 0.12);
}
.card-kicker {
  font-size: 12px;
  font-weight: 600;
  text-transform: uppercase;
  letter-spacing: 0.04em;
  color: #0c66e4;
}
.card h3 { margin: 8px 0 4px; font-size: 17px; }
.card p { margin: 0; font-size: 14px; color: #44546f; }

Links inside the macro open through Confluence's own navigation, so internal /wiki/... links behave like normal page links.

2. Embed videos, maps and design files

When you need it: a product demo video next to the release notes, an office map on the "Getting here" page, a Figma prototype in the design spec.

The built-in iFrame macro works when the site allows embedding and you only need the embed itself. An HTML macro helps when you want the embed wrapped in your own layout, such as a responsive 16:9 frame with a caption, or several embeds side by side.

HTML

<figure class="embed">
  <div class="frame">
    <iframe
      src="https://www.youtube.com/embed/VIDEO_ID"
      title="Release 4.2 walkthrough"
      allowfullscreen
    ></iframe>
  </div>
  <figcaption>Release 4.2 walkthrough (6 minutes)</figcaption>
</figure>

CSS

.embed { margin: 0; }
.frame {
  position: relative;
  aspect-ratio: 16 / 9;
  border-radius: 10px;
  overflow: hidden;
  background: #091e42;
}
.frame iframe {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  border: 0;
}
figcaption { margin-top: 8px; font-size: 13px; color: #44546f; }

Replace VIDEO_ID with your video's ID. In HTML Macro+, unless your admin allows all domains, youtube.com must be on the domain whitelist; until it is, the frame shows a "Content blocked" placeholder. The same applies to google.com for Maps and figma.com for Figma. See security settings.

3. Show an existing HTML file on the page

When you need it: you already have HTML output from another tool, like a test coverage report, a notebook exported to HTML, a generated API reference or a one-page prototype. Attached to a page, it's just a download link that most readers never open.

HTML Macro+ includes an HTML from Attachment macro for this:

Attach the .html file to the Confluence page, or upload it from your computer in the macro.
Insert the HTML from Attachment macro and pick the file.
Publish. The file renders on the page, sized to its content, with the same security rules as any other macro.

When the report is regenerated, replace the attachment to show the new version, with no copying and pasting of generated code.

4. Add interactivity with JavaScript

When you need it: content that's easier to read when readers can switch or filter it, such as tabs for different operating systems, a filterable list, a calculator or a chart.

Here's a small tabbed panel. The same pattern works for any "show one of several" content.

HTML

<div class="tabs">
  <div class="tab-buttons" role="tablist">
    <button class="active" data-tab="mac" role="tab">macOS</button>
    <button data-tab="windows" role="tab">Windows</button>
    <button data-tab="linux" role="tab">Linux</button>
  </div>
  <div class="tab-panel active" id="mac">Install with Homebrew: <code>brew install our-cli</code></div>
  <div class="tab-panel" id="windows">Install with winget: <code>winget install OurCo.Cli</code></div>
  <div class="tab-panel" id="linux">Install with apt: <code>sudo apt install our-cli</code></div>
</div>

CSS

.tabs { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; }
.tab-buttons { display: flex; gap: 4px; border-bottom: 1px solid #dfe1e6; }
.tab-buttons button {
  padding: 8px 14px;
  border: 0;
  border-bottom: 2px solid transparent;
  background: none;
  font-size: 14px;
  color: #44546f;
  cursor: pointer;
}
.tab-buttons button.active { color: #0c66e4; border-bottom-color: #0c66e4; font-weight: 600; }
.tab-panel { display: none; padding: 16px 2px; font-size: 14px; }
.tab-panel.active { display: block; }
code { background: #f1f2f4; padding: 2px 6px; border-radius: 4px; }

JavaScript

document.querySelectorAll(".tab-buttons button").forEach((button) => {
  button.addEventListener("click", () => {
    document
      .querySelectorAll(".tab-buttons button, .tab-panel")
      .forEach((el) => el.classList.remove("active"));
    button.classList.add("active");
    document.getElementById(button.dataset.tab).classList.add("active");
  });
});

For bigger examples, see how to embed interactive charts with Chart.js and how to build a status dashboard.

5. Keep migrated Data Center HTML pages working

When you need it: you're moving from Confluence Server or Data Center, and some pages were built with the HTML macro. After migration, those pages show an "unknown macro" error in Cloud.

HTML Macro+ recognizes both the Server/Data Center HTML macro and the Macro Toolbox for Cloud HTML macro. Once it's installed on your Cloud site, migrated pages render again without editing them one by one. You can then scan a space for the old macros, preview what will change, and convert them in bulk to the current macro. Pages stay live throughout.

Before migrating, check which HTML macros use external scripts or images. Those domains need to be whitelisted in Cloud, or the content will show as blocked.

HTML macro not working?

Most problems come down to a domain that isn't whitelisted, a script that runs before the page is ready, or restricted editor access. The troubleshooting guide walks through each fix.

Frequently asked questions

Can Confluence Cloud render HTML?
Not natively. Confluence Cloud has no HTML macro. You can embed other web pages with the iFrame macro, or install an HTML macro app to render your own HTML, CSS and JavaScript.

Why doesn't Confluence Cloud have an HTML macro?
Letting any editor run their own code on a page is a security risk, especially cross-site scripting. HTML macro apps handle this by rendering code in a sandboxed frame and letting admins control which external sites can load.

Can I paste HTML into the Confluence editor?
Pasting copied web content keeps much of its formatting, but pasting raw HTML code shows it as text. To have code rendered, put it in an HTML macro.

Is it safe to use JavaScript in Confluence Cloud?
It depends on the app. Look for sandboxed rendering, an admin-controlled domain whitelist, and editor permissions so only trusted people can change code. HTML Macro+ has all three, and runs on Atlassian Forge, so content stays inside Atlassian.

Does CSS in the macro change the rest of my Confluence page?
No. Styles apply only to the content inside the macro.

Try it

HTML Macro+ for Confluence is free on the Atlassian Marketplace. Start with the installation guide, then try any example above.

Install HTML Macro+ — free on the Atlassian Marketplace

What Confluence's Built-In PDF Export Can't Do

Yamuno — Wed, 23 Sep 2026 09:27:29 +0000

What Confluence's Built-In PDF Export Can't Do

Confluence's native PDF export is fine when you need one page as a quick PDF. The moment you need more than that, a set of pages, a branded document, or a consistent format, you run into its limits fast. This is an honest list of what the built-in export cannot do, so you can tell when you have outgrown it.

None of this is a knock on Confluence. The native export is a convenience feature, not a document tool. Knowing where it stops is the fastest way to decide whether you need something more.

It Exports One Page at a Time

This is the big one. Native export is built around a single page. There is no way to select several pages, export a parent page together with all of its children, or export a whole space to PDF in one action.

If you need to turn a 40-page documentation set into PDFs, native export means opening each page and exporting it individually, then dealing with 40 separate files. For anything beyond a handful of pages, that stops being practical.

No Cover Page

There is no option to add a title page, a logo, a subtitle, or a document date to the front of the export. The PDF starts straight at the page content. For an internal draft that is fine. For a document going to a client or an executive, the missing cover is the first thing people notice.

No Custom Headers, Footers, or Page Numbers

Native export gives you no control over headers and footers. You cannot add your company name, a document title, a confidentiality line, the export date, or page numbers. Everything a formal document usually carries in the margins is simply absent.

No Watermarks

There is no way to stamp a PDF with "DRAFT", "CONFIDENTIAL", or "FOR REVIEW". For teams that share documents externally or work under compliance rules, a watermark is often a requirement rather than a nicety, and native export does not offer one.

No Reusable Templates

Every native export is a one-off. There is no way to save a format and apply it again, so two exports of the same page a week apart can look different, and two people on the same team have no shared standard to work from. Consistency has to be enforced by hand, which means it usually is not.

No Table of Contents

A single-page native export has no navigation. There is no auto-generated table of contents built from your headings, which is exactly what a longer document needs to be readable once it is a PDF.

Limited Control Over Layout

Native export gives you no say over fonts, margins, line spacing, or page breaks. Wide tables and large images are handled with whatever defaults Confluence applies, and you cannot adjust them. When the output does not fit the page well, there is no setting to fix it.

When You've Outgrown Native Export

If you only ever export the occasional single page for your own use, the built-in export is genuinely all you need, and there is no reason to add an app.

You have outgrown it the moment any of these becomes true:

You need to export more than a few pages at once, or a whole space
The PDF is going to someone outside your team, so it needs a cover and branding
You are exporting for compliance or retention, so it needs watermarks, page numbers, and a repeatable format
You want every export to look the same, which means templates

That is the point where a dedicated export tool earns its place. PDF Exporter for Confluence adds exactly what the native export leaves out: bulk export of multiple pages, page trees, and whole spaces; cover pages, headers, footers, and watermarks; a table of contents; and reusable templates so every export is consistent. It runs on Atlassian Forge, so nothing leaves your instance.

For a step-by-step walkthrough, see How to Export Confluence Pages to PDF.

Getting Started

Install PDF Exporter for Confluence from the Atlassian Marketplace.

Full documentation is at /docs/pdf-exporter-for-confluence.

Questions? Reach out via our support portal.

How Compliance Teams Export Confluence Content to PDF

Yamuno — Wed, 29 Jul 2026 10:41:07 +0000

How Compliance Teams Export Confluence Content to PDF

Compliance teams deal with a recurring documentation challenge: processes, policies, and controls are maintained in Confluence (where they're easy to update and collaborate on), but auditors, regulators, and legal teams need point-in-time PDF snapshots they can review, sign off on, or attach to a submission.

Confluence's native PDF export works for basic cases but has no provisions for the requirements that matter in compliance contexts: consistent formatting across all exported documents, watermarks for draft and confidential status, a clear record of what was exported and when, and reusable templates that ensure every export looks the same regardless of who ran it.

This guide covers how to set up a compliant export workflow using PDF Exporter for Confluence.

The Core Requirements for Compliance Exports

Before configuring anything, it helps to be specific about what compliance exports actually need:

Consistency — every exported document should look the same. If an auditor compares two policy documents and they have different headers, different page layouts, or different cover pages, it raises questions about process.

Document identification — the PDF should identify itself: what it is, who produced it, what classification it carries (confidential, internal, public). This information should be in the header, footer, or cover page — not just in the filename.

Watermarks where required — draft documents under review must be marked as drafts. Confidential documents must be visibly marked. Documents that have been superseded should carry an "ARCHIVED" watermark.

Completeness — when a compliance submission requires a set of documents (all policies in a space, all runbooks for a system), the export should cover the complete set, not a manually assembled selection that could be incomplete.

Step 1 — Set Up Compliance Templates

Create dedicated templates for compliance use cases. Log into Confluence as an admin, go to Settings → PDF Exporter → Templates, and create the following:

Template 1: "Policy — Current"

For active, approved policies shared with auditors or regulators.

Cover style: Executive (minimal, formal)
Accent color: Company primary color
Logo: Company logo
Author: "Compliance Team" or department name
Header: Document title, centered
Footer (left): "Confidential — [Company Name]"
Footer (right): Page number (Page 1 of 10 format)
Watermark: Disabled
Table of contents: Enabled, depth 2
Page breaks: Before H1

Template 2: "Policy — Draft"

For documents under internal review before approval.

Same as "Policy — Current" except:
Watermark: Enabled, text "DRAFT", opacity 0.20
Subtitle: "For Internal Review Only"

Template 3: "Compliance Archive"

For historical snapshots being archived or submitted as evidence of past state.

Same as "Policy — Current" except:
Watermark: Enabled, text "ARCHIVED", opacity 0.15
Footer (left): "Archived — [Company Name] — [Date]"

Note: the footer date needs to be manually updated when creating each archive export, since templates don't have dynamic date fields.

Step 2 — Export Individual Policies

For exporting a single policy document:

Open the policy page in Confluence
Click ••• → Export to PDF
Select the appropriate template ("Policy — Current" for finalized, "Policy — Draft" for review)
Use the Preview option to verify the cover page, watermark, and footer before downloading
Download the PDF

The preview step is important for compliance exports — it takes 15 seconds and catches issues (wrong watermark status, missing logo) that would be unprofessional in a submission.

Step 3 — Export a Complete Policy Set

When an audit requires a complete set of documents — all security policies, all change management procedures, all GDPR-related documentation — use the space export to capture everything in scope.

From the Confluence global navigation, open Apps → PDF Exporter for Confluence
The page tree for the current space is displayed
Navigate the tree and select all pages in scope
Uncheck any pages that are internal working drafts not intended for the submission
Select the "Policy — Current" template
Export

The download is a ZIP file containing one PDF per page. The ZIP structure mirrors the Confluence page hierarchy — auditors can navigate it like a folder structure.

If the submission requires a single combined document rather than individual PDFs, export a parent page with all child pages included — the output is still individual PDFs per page, but they can be manually combined using any PDF tool if a single-file format is required.

Step 4 — Archive Snapshots

Compliance often requires preserving point-in-time snapshots of policies — what did the data retention policy say on January 1, 2026? The page in Confluence may have been updated since then.

The workflow for archive snapshots:

When a policy is approved, export it immediately using the "Policy — Current" template
Store the PDF in a designated archive location (shared drive, document management system)
When the policy is updated and re-approved, export the updated version and archive the previous one using the "Compliance Archive" template (which adds the ARCHIVED watermark)

This gives you a complete versioned record: the current approved policy in Confluence, and a series of archived PDFs showing the policy's state at each approval milestone.

Step 5 — Document the Export Process Itself

For audits where the reviewer may ask "how do you ensure the exported documents are accurate?", document the export process itself in Confluence:

Which templates are used for which document types
Who is authorized to run compliance exports
How and where archived PDFs are stored
The review/preview step that happens before each export

This process documentation can itself be exported to PDF using the same templates. An auditor asking "what's your document control process?" gets a PDF produced by the same process it describes.

Common Compliance Scenarios

SOC 2 audit preparation: Export all security policies (access control, change management, incident response, business continuity) using the "Policy — Current" template. The cover page identifies the document; the consistent header and footer identify the producing organization; the table of contents makes it navigable.

GDPR documentation submission: Export privacy policy, data processing agreements, and DPIA records. Use the "Policy — Current" template. Ensure the footer carries the confidentiality classification appropriate for GDPR documentation.

ISO 27001 evidence collection: Export control documentation, risk assessment records, and procedure documents. For evidence of past state ("what did your risk assessment look like during the audit period?"), use archived snapshots from the archive workflow above.

Legal hold: When content in Confluence becomes subject to a legal hold, export the relevant pages immediately using the "Compliance Archive" template and store them outside Confluence where they can be produced on request.

Install PDF Exporter for Confluence →

Read the documentation →

How to Bulk Import Markdown Files into Confluence

Yamuno — Thu, 23 Jul 2026 10:24:54 +0000

How to Bulk Import Markdown Files into Confluence

If you're migrating documentation from GitHub, GitLab, Notion, or a static site generator, you're probably looking at more than a handful of markdown files. Importing them one at a time into Confluence isn't viable at scale. This guide covers how to bulk import — dozens or hundreds of files at once — with the page hierarchy, images, and formatting preserved.

What "Bulk Import" Means in Practice

A bulk import takes a ZIP archive containing markdown files and a folder structure, and creates a matching set of Confluence pages with the same hierarchy. A folder in the ZIP becomes a parent page in Confluence. A markdown file becomes a Confluence page. Images referenced in the markdown are uploaded as attachments and linked correctly in the page content.

The result: a ZIP with 80 files becomes 80 Confluence pages in the right hierarchy without anyone touching each one individually.

Step 1 — Prepare Your Markdown Files

Install Markdown Importer for Confluence from the Atlassian Marketplace.

Before creating the ZIP, organize your markdown files in the folder structure you want reflected in Confluence:

docs/
├── getting-started.md
├── installation.md
├── configuration/
│   ├── basic-setup.md
│   ├── advanced-options.md
│   └── environment-variables.md
├── how-to/
│   ├── first-steps.md
│   └── common-tasks.md
└── reference/
    ├── api.md
    └── cli.md

Each folder will become a parent page in Confluence. The nesting can be as deep as you need.

File naming: The importer uses the markdown filename (without the .md extension) as the Confluence page title. Hyphens are replaced with spaces and the first letter is capitalized — getting-started.md becomes "Getting Started." If a file has a title field in its frontmatter, that takes precedence over the filename.

Step 2 — Add Frontmatter (Optional but Recommended)

YAML frontmatter at the top of each markdown file gives the importer more information to work with:

---
title: "Advanced Configuration Options"
---

# Advanced Configuration Options

Rest of the content...

If a title is present, the importer uses it as the Confluence page title. This lets you have descriptive filenames in the repo while setting human-readable titles in Confluence.

Other frontmatter fields are not processed by the importer but are preserved if you later export back to markdown.

Step 3 — Include Images in the ZIP

If your markdown files reference local images, include them in the ZIP alongside the markdown files:

docs/
├── getting-started.md          # references ./images/screenshot.png
├── images/
│   └── screenshot.png
└── reference/
    ├── api.md                  # references ../images/api-flow.png
    └── cli.md

Image references in the markdown should be relative paths:

![Screenshot](./images/screenshot.png)

The importer uploads the images as Confluence attachments and updates the references in the page content to point to the uploaded attachments. The relative path structure is resolved relative to the markdown file's location in the ZIP.

Step 4 — Create the ZIP Archive

On macOS or Linux:

cd /path/to/your
zip -r docs-import.zip docs/

On Windows (PowerShell):

Compress-Archive -Path .\docs\ -DestinationPath .\docs-import.zip

The ZIP should contain the root folder (docs/), not just the contents. This preserves the top-level folder name, which becomes the title of the root-level parent page if you're importing the whole tree.

If you'd rather the import start with the contents of the folder (not the folder itself as a parent page), zip the contents directly:

cd /path/to/your/docs
zip -r ../docs-import.zip .

Step 5 — Import the ZIP

Navigate to the Confluence page that should be the parent of the imported content
Click ••• (More actions) → Markdown Importer & Exporter
Click Upload and select your ZIP archive
Configure the import options:
- Page Hierarchy — enable this to create parent/child pages from the folder structure
- Overwrite existing pages — enable if you're re-importing and want to update pages that already exist
Click Import

A progress indicator shows pages being processed. For large imports (100+ pages), this may take a few minutes. The importer processes pages in small batches to avoid hitting Confluence API rate limits.

Step 6 — Import from the Global Apps Menu (Multiple Spaces)

If you're importing into multiple Confluence spaces in one operation, use the global access point instead of the page-level entry:

Click Apps in the Confluence global navigation
Select Markdown Importer & Exporter
Choose the target space and parent page from the dropdowns
Upload your ZIP and configure options
Import

Admins can use this to import documentation across multiple spaces without navigating to each target page individually.

Handling Large Imports

For very large imports (500+ pages), consider splitting the ZIP by section and importing in batches. This makes it easier to review the output after each batch and fix any issues before continuing.

After the first batch, check a few imported pages to verify:

Page titles are correct
Images are displaying (not showing broken links)
The hierarchy is correct in the page tree
Formatting (code blocks, tables, headings) rendered properly

If something is off, it's usually a consistent issue (like image paths being wrong) that you can fix across all remaining files before the next batch.

Common Issues

Broken image references: Usually caused by images being outside the ZIP or using absolute paths instead of relative paths. Fix the markdown to use relative paths and ensure images are inside the ZIP.

Wrong page titles: The filename is being used instead of frontmatter. Add title: frontmatter to the affected files.

Hierarchy not matching the folder structure: Page Hierarchy option was not enabled during import. Re-import with the option enabled — use "Overwrite" to update the existing pages.

Import stops partway through: Likely a rate limit from the Confluence API. Wait a few minutes and re-import the remaining files. Use "Overwrite" so already-imported pages are updated rather than duplicated.

Install Markdown Importer for Confluence →

Read the documentation →

How to Build a Custom Status Dashboard in Confluence

Yamuno — Sat, 18 Jul 2026 09:35:48 +0000

How to Build a Custom Status Dashboard in Confluence

Project status pages in Confluence often end up as paragraphs of text that nobody reads. A wall of prose with a last-updated date from three weeks ago doesn't communicate project health — it communicates that someone was busy when they wrote it.

A visual status dashboard that shows RAG indicators, progress percentages, and days until key milestones is faster to read and easier to maintain. This guide walks through building one using HTML Macro for Confluence.

What We're Building

A status dashboard with four components:

RAG status cards — one per workstream, color-coded by health
Progress bars — percentage complete for each initiative
Milestone countdown — days until the next key date
Metric tiles — key numbers at a glance

Each component is a separate HTML Macro on the page. You can use all four or just the ones that fit your context.

Component 1 — RAG Status Cards

A row of status cards, one per workstream. Color-coded: green = on track, amber = at risk, red = blocked.

<div style="display:flex; gap:16px; flex-wrap:wrap; font-family:sans-serif;">

  <div style="flex:1; min-width:180px; padding:20px; border-radius:12px; background:#f0fdf4; border:1px solid #86efac;">
    <div style="font-size:12px; font-weight:600; text-transform:uppercase; letter-spacing:0.08em; color:#15803d; margin-bottom:8px;">Backend API</div>
    <div style="display:flex; align-items:center; gap:8px;">
      <div style="width:12px; height:12px; border-radius:50%; background:#22c55e; box-shadow:0 0 6px #22c55e88;"></div>
      <span style="font-size:15px; font-weight:700; color:#1e293b;">On Track</span>
    </div>
    <div style="margin-top:8px; font-size:13px; color:#64748b;">Sprint 3 of 4 complete</div>
  </div>

  <div style="flex:1; min-width:180px; padding:20px; border-radius:12px; background:#fffbeb; border:1px solid #fcd34d;">
    <div style="font-size:12px; font-weight:600; text-transform:uppercase; letter-spacing:0.08em; color:#92400e; margin-bottom:8px;">Mobile App</div>
    <div style="display:flex; align-items:center; gap:8px;">
      <div style="width:12px; height:12px; border-radius:50%; background:#f59e0b; box-shadow:0 0 6px #f59e0b88;"></div>
      <span style="font-size:15px; font-weight:700; color:#1e293b;">At Risk</span>
    </div>
    <div style="margin-top:8px; font-size:13px; color:#64748b;">Design review delayed 3 days</div>
  </div>

  <div style="flex:1; min-width:180px; padding:20px; border-radius:12px; background:#fef2f2; border:1px solid #fca5a5;">
    <div style="font-size:12px; font-weight:600; text-transform:uppercase; letter-spacing:0.08em; color:#b91c1c; margin-bottom:8px;">Integrations</div>
    <div style="display:flex; align-items:center; gap:8px;">
      <div style="width:12px; height:12px; border-radius:50%; background:#ef4444; box-shadow:0 0 6px #ef444488;"></div>
      <span style="font-size:15px; font-weight:700; color:#1e293b;">Blocked</span>
    </div>
    <div style="margin-top:8px; font-size:13px; color:#64748b;">Waiting on vendor API access</div>
  </div>

</div>

To update a status: change #22c55e → #f59e0b → #ef4444 on both the dot color and the card background/border colors, and update the label and note text.

Component 2 — Progress Bars

Visual progress indicators for each initiative. The percentage is shown as a filled bar with a label.

<div style="font-family:sans-serif; max-width:560px;">

  <div style="margin-bottom:18px;">
    <div style="display:flex; justify-content:space-between; margin-bottom:6px;">
      <span style="font-size:14px; font-weight:600; color:#1e293b;">Backend API</span>
      <span style="font-size:14px; font-weight:700; color:#6366f1;">75%</span>
    </div>
    <div style="background:#e2e8f0; border-radius:99px; height:8px;">
      <div style="background:#6366f1; width:75%; height:8px; border-radius:99px;"></div>
    </div>
  </div>

  <div style="margin-bottom:18px;">
    <div style="display:flex; justify-content:space-between; margin-bottom:6px;">
      <span style="font-size:14px; font-weight:600; color:#1e293b;">Mobile App</span>
      <span style="font-size:14px; font-weight:700; color:#f59e0b;">48%</span>
    </div>
    <div style="background:#e2e8f0; border-radius:99px; height:8px;">
      <div style="background:#f59e0b; width:48%; height:8px; border-radius:99px;"></div>
    </div>
  </div>

  <div style="margin-bottom:18px;">
    <div style="display:flex; justify-content:space-between; margin-bottom:6px;">
      <span style="font-size:14px; font-weight:600; color:#1e293b;">Integrations</span>
      <span style="font-size:14px; font-weight:700; color:#ef4444;">20%</span>
    </div>
    <div style="background:#e2e8f0; border-radius:99px; height:8px;">
      <div style="background:#ef4444; width:20%; height:8px; border-radius:99px;"></div>
    </div>
  </div>

</div>

To update: change the width percentage on the filled div and the number in the label. Match the bar color to the RAG status from Component 1.

Component 3 — Milestone Countdown

A JavaScript countdown to the next key date.

<div style="font-family:sans-serif; display:inline-flex; align-items:center; gap:24px; padding:20px 28px; background:#f8fafc; border:1px solid #e2e8f0; border-radius:14px;">
  <div>
    <div style="font-size:12px; font-weight:600; text-transform:uppercase; letter-spacing:0.08em; color:#64748b; margin-bottom:4px;">Launch Date</div>
    <div style="font-size:14px; color:#1e293b; font-weight:500;">August 15, 2026</div>
  </div>
  <div style="display:flex; gap:16px; text-align:center;">
    <div>
      <div id="cd-days" style="font-size:40px; font-weight:800; color:#1e293b; line-height:1;">--</div>
      <div style="font-size:11px; color:#94a3b8; text-transform:uppercase; letter-spacing:0.06em; margin-top:3px;">Days</div>
    </div>
    <div style="font-size:32px; color:#e2e8f0; font-weight:300; padding-top:4px;">:</div>
    <div>
      <div id="cd-hours" style="font-size:40px; font-weight:800; color:#1e293b; line-height:1;">--</div>
      <div style="font-size:11px; color:#94a3b8; text-transform:uppercase; letter-spacing:0.06em; margin-top:3px;">Hours</div>
    </div>
  </div>
</div>

<script>
  var target = new Date("2026-08-15T09:00:00");
  function tick() {
    var diff = target - new Date();
    if (diff <= 0) {
      document.getElementById("cd-days").textContent = "0";
      document.getElementById("cd-hours").textContent = "0";
      return;
    }
    document.getElementById("cd-days").textContent = Math.floor(diff / 86400000);
    document.getElementById("cd-hours").textContent = Math.floor((diff % 86400000) / 3600000);
  }
  tick();
  setInterval(tick, 60000);
</script>

Change the date string in new Date("2026-08-15T09:00:00") to your actual milestone date.

Component 4 — Metric Tiles

Key numbers at a glance — open issues, completed stories, team size, or any other project metric.

<div style="display:flex; gap:16px; flex-wrap:wrap; font-family:sans-serif;">

  <div style="flex:1; min-width:140px; padding:20px; border-radius:12px; background:#fff; border:1px solid #e2e8f0; text-align:center;">
    <div style="font-size:36px; font-weight:800; color:#6366f1;">34</div>
    <div style="font-size:13px; color:#64748b; margin-top:4px;">Issues Closed</div>
  </div>

  <div style="flex:1; min-width:140px; padding:20px; border-radius:12px; background:#fff; border:1px solid #e2e8f0; text-align:center;">
    <div style="font-size:36px; font-weight:800; color:#22c55e;">12</div>
    <div style="font-size:13px; color:#64748b; margin-top:4px;">Open Bugs</div>
  </div>

  <div style="flex:1; min-width:140px; padding:20px; border-radius:12px; background:#fff; border:1px solid #e2e8f0; text-align:center;">
    <div style="font-size:36px; font-weight:800; color:#f59e0b;">3</div>
    <div style="font-size:13px; color:#64748b; margin-top:4px;">Blocked Items</div>
  </div>

  <div style="flex:1; min-width:140px; padding:20px; border-radius:12px; background:#fff; border:1px solid #e2e8f0; text-align:center;">
    <div style="font-size:36px; font-weight:800; color:#1e293b;">8</div>
    <div style="font-size:13px; color:#64748b; margin-top:4px;">Team Members</div>
  </div>

</div>

To update: change the number inside the large div and the label below it. Update the color to reflect the health of the metric if relevant (green for good, amber for concerning, red for problem).

Putting It Together

On the Confluence page, add four HTML Macro blocks stacked vertically:

RAG Status Cards at the top
Metric Tiles below
Progress Bars in the middle
Milestone Countdown at the bottom

Add a native Confluence "Last Updated" text or use the @date mention to timestamp the page. This tells readers whether the data is current.

Weekly update workflow: At the start of each week, open the page, click Edit, and update the RAG color/label in each card, the progress bar percentages, and the metric numbers. It takes 5–10 minutes and the page communicates project health clearly to anyone who opens it.

Install HTML Macro for Confluence — free on the Atlassian Marketplace

Jira Reporting for Product Managers: Charts, Metrics, and Dashboards

Yamuno — Tue, 14 Jul 2026 10:00:30 +0000

Jira Reporting for Product Managers: Charts, Metrics, and Dashboards

Product managers and engineering teams look at the same Jira data and need completely different things from it. Engineering wants sprint health, cycle time, and blocked issue counts. Product management wants feature progress, release readiness, customer-reported bug trends, and backlog composition.

Most Jira dashboards are set up by or for engineering teams. If you're a PM who has tried to get useful reporting out of Jira and ended up with a page full of gadgets that don't answer your actual questions, this guide is for you.

The Four Questions a PM Dashboard Should Answer

Before picking any chart, start with the questions:

What's the state of the current release? — Feature completion, open bugs, scope changes
What's the trend for customer-reported issues? — Bug volume over time, resolution rate
What does the backlog look like? — Priority distribution, backlog by product area
What shipped recently? — Completed features, closed bugs, release notes fodder

If your dashboard can answer these four questions without anyone opening a filter or running a query, it's doing its job.

Chart 1 — Release Progress Bar

The question: How far along are we in the current release?

Setup:

Chart type: Bar (stacked)
Filter: fixVersion = "Your Release Name"
Group by: Status
Show: To Do, In Progress, In Review, Done as stacked segments

A stacked bar with one bar showing all four statuses tells you at a glance: how much is done, how much is in flight, and how much hasn't started. When the Done segment is 80%+ of the bar with a week left in the release, you're in good shape. When To Do still represents 40% with the release date looming, you have a scope problem.

JQL filter:

project = YOURPROJECT AND fixVersion = "v2.4" AND issueType in (Story, Bug, Task)

Chart 2 — Customer-Reported Bug Trend

The question: Is the volume of customer-reported bugs stable, increasing, or decreasing?

Setup:

Chart type: Line
Filter: label = "customer-reported" (or however your team tags customer bugs)
X-axis: Week or month
Y-axis: Issue count created in that period

This chart is most useful over a 90-day window. A stable horizontal line means your product quality is consistent. An upward trend after a release means the release introduced regressions. A downward trend is good news — though confirm it's not just a drop in reporting.

If your team doesn't use a consistent label for customer-reported issues, this is the right time to establish one. The reporting value is significant.

Chart 3 — Feature vs. Bug Ratio in the Backlog

The question: Is the backlog dominated by one type of work?

Setup:

Chart type: Pie or donut
Filter: Open issues in the project
Group by: Issue type

For a product team, the ideal ratio depends on the product maturity stage. A new product might be 80% features and 20% bugs. A mature product with a large install base might be 50/50. What you're watching for is a trend — if the bug proportion grows every quarter, quality investment is falling behind.

This is also useful for product strategy conversations: when engineering says they need a "bug bash sprint," this chart gives you the data to support (or challenge) the request.

Chart 4 — Backlog by Priority

The question: How much of the backlog is urgent?

Setup:

Chart type: Bar (horizontal)
Filter: Open issues in backlog
Group by: Priority

A priority bar chart shows how the backlog breaks down by Critical, High, Medium, and Low. The ratio matters: a backlog that's 30% Critical and 40% High is telling you that your priority labels have inflated to the point of meaninglessness, or that there's genuinely too much urgent work and the team can't keep up.

Review this chart before each quarterly planning cycle. If the High bar keeps growing despite the team working on High-priority issues, capacity is mismatched with demand.

Chart 5 — Completed Work by Area

The question: What shipped this quarter, and in which product areas?

Setup:

Chart type: Bar
Filter: status = Done AND updated >= -90d
Group by: Label (product area labels) or Component

This chart is a retrospective view of where the team's output went. If you have labels for product areas ("auth," "billing," "reporting," "mobile"), a bar chart of completed issues by label shows what got attention. It's a useful starting point for "was this the quarter we said we'd focus on X?" conversations.

Also useful for release notes compilation — filter to the release's fixVersion and group by issue type to see what categories of work shipped in that release.

Setting Up the PM Dashboard

Create a dedicated Jira dashboard for product management. Don't share the sprint team's dashboard — the audiences and refresh cadences are different.

Recommended layout — three columns:

Left column	Center column	Right column
Release progress (bar)	Customer bug trend (line)	Backlog by priority (bar)
Feature vs. bug ratio (pie)	Completed by area (bar)	(empty or a filter results table)

Add a date range selector at the top if Charts for Jira supports a shared filter — change the range and both time-based charts update together.

Share it: Add the Confluence team, the engineering manager, and any design leads as viewers. A shared dashboard replaces the "can you pull the Jira report for the leadership update?" request with a link they can check themselves.

What Good Jira Reporting Looks Like

The sign that your dashboard is working: you open it in a meeting, look at it for 30 seconds, and can answer questions from it without typing a single JQL query. If you're still exporting to spreadsheet to get the answer you need, the dashboard isn't answering the right questions yet.

Start with the release progress chart and the bug trend. Those two alone are more valuable than most Jira dashboards that have eight gadgets.

Install Charts for Jira Dashboard →

Problem	Cause	Fix
The rest of the paragraph turns italic	A missing closing `$`	Close the math, or switch to `\(...\)` so the error is reported
Words inside an equation run together	Text typed in math mode	Wrap words in `\text{}`
An inline fraction looks tiny	Inline style is applied	Use `\dfrac` once, or move the equation to display math
Lines in the paragraph spread apart	A tall inline expression	Put the equation on its own line with `\[...\]`
A price prints as math	`$` read as a delimiter	Escape it as `\$`

DEV Community: Yamuno Software

Script Toolkit for Jira is live on the Marketplace

Script Toolkit for Jira is live on the Marketplace

What you can build

Try code in the Script Console

Fragments: your own panels inside Jira

Dashboard gadgets

Web triggers for other systems

Scheduled jobs

Scripted fields

Workflow validators and post-functions

Bulk tools for people who aren't admins

Safe by default

Who it's for

Getting started

Frequently asked questions

How much does Script Toolkit cost?

Which language are scripts written in?

Who can write scripts?

Do scripts run on external servers?

Can a backend script change Jira?

Can I test a script before it goes live?

Try it

Issue History+ for Jira is live on the Marketplace

Issue History+ for Jira is live on the Marketplace

What the app does

Search the change history of many issues at once

Time in status

Status timeline

Insights

Issue Insights on every issue

Restore

Reports for people outside Jira

Your data stays in Atlassian

Who it's for

Getting started

Frequently asked questions

How much does Issue History+ cost?

Where does the history come from?

Can people see history for issues they can't access?

Does it work with company-managed and team-managed projects?

Does it change anything in Jira?

Try it

PDF Exporter adds scheduled exports and a REST API

PDF Exporter adds scheduled exports and a REST API

Background exports and My exports

Scheduled exports

Email notifications without noise

Failures you can act on

A REST API for scripts and pipelines

Fair use: one server export at a time

Smaller changes and fixes

Frequently asked questions

Do I need to do anything to get the new features?

Do small exports still happen in my browser?

How long are background exports kept?

Can a scheduled export run at a set time of day?

What can the REST API export?

Does any of this send data outside Atlassian?

Try it

Confluence Markup: Wiki Markup vs Markdown in Cloud

Confluence Markup: Wiki Markup vs Markdown in Cloud

What is Confluence markup?

Markdown in the Confluence Cloud editor

Wiki markup vs Markdown, side by side

Confluence wiki markup cheat sheet

Which one should you use?

Converting between the two

Keeping Markdown as Markdown in Confluence

Frequently asked questions

What is the Confluence markup language?

Does Confluence Cloud still support wiki markup?

Can I write Markdown in Confluence Cloud?

What is the difference between Confluence markup and Markdown?

How do I convert Confluence wiki markup to Markdown?

Can I paste a README into Confluence and keep its formatting?

Try it

LaTeX Inline Math: $...$, \\(...\\) and Display Math

LaTeX Inline Math

$...$ or \(...\)?