Jira Server (and Data Center)
How the extension behaves on Jira Server — toolbar injection, wiki markup, custom toolbar configuration.
Jira Server (also called Jira Software Server or Jira Data Center) uses the legacy Atlassian rich text editor. The extension injects directly into that editor.
Where the UI appears
When you open a create-issue dialog, three additions appear in/around the description field:
- Toolbar with template buttons — one button per template that has the “quick-access buttons” toggle on.
- Template dropdown — a single dropdown above the editor listing every matching template.
- Right-click menu items — the browser context menu gains a “Templates” submenu.
Wiki markup vs rich text
Jira Server’s editor accepts wiki markup (*bold*, # Header, etc.) as well as rich text. The extension supports both:
- Rich text templates — author in the editor’s WYSIWYG mode in the options page; insert as HTML.
- Wiki markup templates — toggle “Wiki mode” in the editor; the right pane shows a live HTML preview.
The wiki preview supports the most common Jira macros:
| Macro | Preview rendering |
|---|---|
{panel:title=Story}…{panel} | A bordered box with optional title bar |
{code:java}…{code} | A monospace code block |
{quote}…{quote} | An indented blockquote |
{noformat}…{noformat} | Preformatted plain text |
Note: The preview is approximate — Jira Server’s actual renderer may produce slightly different output.
Both modes insert correctly into Jira Server. Pick whichever feels more natural to you.
Custom toolbar
Some Jira Server instances configure the editor’s toolbar in a non-standard way. The extension’s “Custom toolbar” setting (in Settings) lets you specify which toolbar to inject the template buttons into.
Tip: If your toolbar isn’t appearing in the standard place, enable Custom toolbar mode and provide the CSS selector of your editor’s toolbar. The default selector covers ~95% of installations.
Comments
Comments use the same editor but a slightly different DOM structure. The extension detects comment fields automatically and injects the same UI. Comment templates use issue type Comment.
Known limitations
- Inline edit forms (clicking directly on the description in the issue view) work but are sometimes affected by Atlassian’s auto-save logic. If the template content disappears, click out and back in to re-trigger.
- Iframe editors in some custom Atlassian apps are not currently supported.