Jira Ticket Template Quick-Filler

WHAT IT DOES

This userscript eliminates repetitive ticket creation by allowing you to save and instantly apply templates to Jira issue forms. It reads all fields from Jira's create and edit forms including summary, description, priority, assignee, labels, fix versions, components, and custom fields. With one click, a saved template fills all mapped fields simultaneously. The script supports powerful variable substitution - use placeholders like {{date}} for today's date, {{user}} for the current user, {{project}} for the project key, or define your own custom variables. You can save templates from existing tickets or build them manually field by field. Templates are stored locally and can be exported and imported for sharing across devices.

WHERE IT RUNS

The script activates on all Jira Cloud pages containing issue forms, including the Create Issue dialog, Edit Issue screens, and individual issue view pages. It works across all Atlassian Jira instances (atlassian.net) and detects both standard fields and custom fields dynamically.

HOW TO USE

After installation, open any Jira create or edit form. The script detects available fields and displays them in the panel. To save the current ticket as a template, enter a name and click Save - the script captures all non-empty field values. To create a template manually, select a field from the dropdown, enter a value, and add it to the template. Click any template in the list to instantly apply it to the current form. Use variable placeholders like {{date}} in field values for dynamic content. Configure auto-fill to automatically apply a template when the page loads. Export your templates as JSON for backup or sharing.

THE ACTUAL REASON IT WORKS

Unlike form-filling extensions that rely on fixed field selectors, this script dynamically discovers Jira's form fields using a multi-strategy approach. It scans for inputs, textareas, selects, comboboxes, and rich text editors (ProseMirror), then finds associated labels via for/id attributes, aria-labels, data-testid patterns, and placeholder text. When applying a template, the script performs intelligent field matching using both exact and partial label matching. For React-controlled fields, it dispatches both "input" and "change" events after setting values to ensure Jira's React components properly update their internal state. The variable substitution engine supports both system variables (date, time, user, project) and custom user-defined variables, with recursive substitution for nested references.

THE PANEL

The panel is fully draggable by its header and remembers its position across page loads using GM_setValue. It collapses to a small icon when minimized, preserving screen space. Press Escape or click the × button to close the panel. The panel includes a list of saved templates, a form for saving current tickets, a manual template builder with field/value mapping, variable configuration, and import/export controls. Each template shows its name and field count, with Apply and Delete buttons.

PLEASE NOTE

This userscript requires the free BotGentz extension to run. Templates are stored locally in your browser's userscript storage and are not automatically synced across devices (use Export/Import for sharing). The script reads and writes ticket form fields only - it does not access ticket history, comments, or attachments. Jira periodically updates its interface, which may affect field detection; we actively maintain the script for compatibility. Always review filled fields before submitting tickets, especially when using templates with auto-fill enabled. Custom fields are detected dynamically but may require manual mapping if their labels are ambiguous.