Jira Cloud

Jira Cloud uses ProseMirror as its rich text editor — a different technology from Jira Server’s legacy editor. The extension handles Cloud differently to account for this.

Domain detection

The extension uses a two-step approach to recognise Jira Cloud:

1. URL check — if the hostname contains atlassian.net, it’s treated as Cloud immediately.
2. API probe — for custom domains (e.g. jira.yourcompany.com), the extension calls /rest/api/latest/serverInfo and checks whether deploymentType is "Cloud".

Either way, the result is cached per-hostname in chrome.storage.local, so subsequent visits skip the detection step entirely. This means custom Cloud domains work out of the box — as long as the domain is included in your allowed domains.

Where the UI appears

The same three insertion points are available — toolbar buttons, dropdown, and right-click menu — but they’re injected after ProseMirror has finished rendering. There can be a brief 100-200 ms delay on the first visit to a ticket.

How the insert works

The extension writes your template’s HTML directly into ProseMirror’s contenteditable area. ProseMirror then parses and re-renders the HTML according to its own schema. This is a robust approach — it works across Jira Cloud updates without relying on internal Atlassian APIs — but it means ProseMirror decides what to keep and what to discard.

Most common formatting survives the round-trip cleanly:

• Headings (H1 → H6)
• Bold, italic, underline, strikethrough
• Bullet and ordered lists
• Tables
• Links
• Code blocks

Cloud-only templates

You can configure a template to only show on Jira Cloud by setting its platform to “Jira Cloud” in the editor. This is useful when you have markup that only makes sense on Cloud (e.g. specific custom fields).

Comments and detail-view popups

Cloud renders comment fields and popup detail views as separate ProseMirror instances. The extension injects into all of them — but comment templates need to have issue type Comment to autofill.

Editor differences to be aware of

The template editor on the options page shows an approximate preview — the actual rendering in Jira Cloud may differ slightly.

The template editor (TipTap) and Jira Cloud’s editor (ProseMirror) are both rich text editors, but they don’t support the exact same feature set. Content that looks fine in one editor may render differently — or not at all — in the other. This is inherent to how the two editors parse HTML and cannot be fully eliminated.

What works reliably: headings, bold/italic/underline, lists, tables, links, and code blocks. Beyond that, keep these differences in mind:

• Jira Cloud emoticon images (the built-in emoji from Jira’s picker) are preserved when pasted into the template editor. Custom emoji images from other sources may not survive the round-trip.
• Atlassian Smart Links in templates flatten to plain links during insert.
• @-mentions are Jira-internal objects and cannot be represented in a template.
• Media attachments (images uploaded to Jira) are not supported in templates.

Tip: If something looks off after inserting a template, simplify the formatting. Stick to the basics listed above and the result will be consistent across both editors.