Import & export

The extension has no server, so sharing is done by exporting templates as JSON and importing them on the receiving side.

Exporting

In the Settings panel:

1. Click Export templates.
2. The browser downloads a templates.json file with every template plus your settings.

The file is portable — pass it to a teammate via Slack, email, Drive, or anywhere else.

Importing

Drop the JSON file into the Import templates zone in Settings. A merge/overwrite chooser appears:

• Merge — adds the imported templates to your existing list. Duplicates (matching by uuid) are skipped.
• Overwrite — replaces all your templates with the imported set. This is destructive — make sure you’ve exported your current templates first.

After confirming, the import runs and a toast confirms how many templates were added or replaced.

Sync from URL

If your team hosts a shared template file on an internal server, CDN, or cloud storage (e.g. https://intranet.example.com/templates.json), you can import directly from that URL:

1. In the Settings panel, enter the URL into the Sync input field.
2. Click Sync — the same merge/overwrite chooser appears.
3. The extension fetches the JSON, validates it, and applies the templates.

This is handy for keeping everyone on the same set — update the hosted file once and tell the team to hit Sync.

Tip: The URL must point to a publicly reachable (or VPN-accessible) JSON file. The extension performs a regular fetch(), so CORS headers on the server must allow the request from a browser extension origin.

Schema

Each template in the export JSON has these fields:

{
  "uuid": "abc-123",
  "templateName": "Bug report",
  "ticketDesc": "...html or wiki markup...",
  "issueType": "Bug",
  "projects": "default",
  "platform": "all",
  "platformConfig": { "jira": {}, "azureDevOps": {} },
  "quickAccessButton": true,
  "quickAccessDropdown": true,
  "quickAccessContextMenu": true
}

About "projects": "default": in the editor UI you leave the projects field blank to make a template universal. The extension stores that as the literal string "default" for compatibility with the content-script matcher — that’s why you’ll see this token in exports even though you never typed it.

The schema is stable across versions — older v1 exports (without platform / platformConfig) are auto-migrated on import.

Backup before risky changes

Always export before:

• Importing an unfamiliar template set
• Major version upgrades of the extension
• Switching browsers