Troubleshooting

If something isn’t working, walk this list top to bottom. The first three issues account for ~90% of reports.

Templates aren’t appearing in Jira

1. Refresh the page. The extension’s content script runs on document idle; if Jira loaded the form before the script was ready, refreshing is enough.
2. Check the project key. The template’s projects field has to be blank (matches every project) or include the project key shown in the URL (e.g. BROWSE/ABC-123 → project key is ABC).
3. Check the issue type. Spelling matters — Story and User Story are different. Match what your Jira instance actually uses.

Autofill isn’t firing

Same first-three checks as above, plus:

4. “Enable autofill” is off. Go to Settings and turn it on.
5. Description already has content. Autofill won’t overwrite by default — it appends. If you’d prefer overwrite, enable Replace existing content in Settings.

Toolbar buttons are missing but the dropdown works (or vice versa)

Each template has independent toggles for toolbar / dropdown / context menu. Check the template’s editor — make sure the relevant toggle is on.

”Custom toolbar” warnings on Jira Server

If you’ve enabled Custom toolbar mode and the buttons aren’t appearing, the CSS selector probably doesn’t match. Open browser DevTools, find the toolbar element you want to target, and copy its selector. Paste it into the Custom toolbar field in Settings.

Saves not persisting

The extension uses chrome.storage.local, which has a 5 MB hard limit per origin. If you have hundreds of long templates you may be approaching the cap.

• Check your storage quota in DevTools (Application → Storage).
• Trim long templates if you’re close to the limit.
• Export-then-import in chunks if you need to migrate.

Imported templates don’t show up

The import dialog has two modes:

• Merge — keeps existing, adds new (skipping UUID duplicates).
• Overwrite — replaces everything.

If you imported in Merge mode and the imported file has the same UUIDs as your existing templates, nothing visible changes. Re-export the source file with new UUIDs (open it in a text editor, change the uuid strings), then re-import.

Firefox: extension stops working after browser update

Firefox occasionally invalidates extension storage on major upgrades. If your templates vanish:

1. Look in about:addons → Ticket Templates → Preferences for an option to restore.
2. Re-import from your last export.
3. Email the developer (see below) so the upgrade path can be improved.

Reporting a bug

Email steven.wittmann@mail.de with the subject Bug report - Ticket Templates. Useful info to include:

• Browser and version (e.g. Chrome 130, Firefox 128)
• Extension version (visible in the page header, e.g. v2026.4.23)
• Platform (Jira Server / Cloud, Azure DevOps)
• Exact steps to reproduce
• Console errors, if any (F12 → Console)

You can also leave a short bug report as a web-store review — Steven reads every one and responds publicly.