Skip to content

Templates

Save issue configurations as templates for quick reuse.

  • Authenticated profile (atlcli auth login)
  • Jira permission: Browse Projects (to save from existing issues)
Terminal window
atlcli jira template list

Save an existing issue as a template:

Terminal window
atlcli jira template save bug-report --issue PROJ-123

Options:

FlagDescription
--issueSource issue key
--descriptionTemplate description
--forceOverwrite existing template
Terminal window
atlcli jira template get bug-report

Create an issue from a template:

Terminal window
atlcli jira template apply bug-report --project PROJ --summary "Login fails on mobile"

Options:

FlagDescription
--projectTarget project (required)
--summaryIssue summary (required)
--assigneeOverride assignee
Terminal window
atlcli jira template delete bug-report --confirm

Export to a JSON file:

Terminal window
atlcli jira template export bug-report -o ./templates/bug-report.json

Import from a JSON file:

Terminal window
atlcli jira template import --file ./templates/bug-report.json

Templates support hierarchical storage at three levels:

LevelLocationScope
global~/.atlcli/templates/jira/Available everywhere
profile~/.atlcli/profiles/<name>/templates/jira/Available when using profile
project.atlcli/templates/jira/Available in project directory
Terminal window
# Save globally (default)
atlcli jira template save my-template --issue PROJ-123
# Save to profile
atlcli jira template save my-template --issue PROJ-123 --level profile
# Save to project
atlcli jira template save my-template --issue PROJ-123 --level project
Terminal window
atlcli jira template list

Output:

NAME TYPE FIELDS LEVEL DESCRIPTION
bug-report Bug 5 [global] Standard bug report
feature-request Story 4 [profile:work] Team feature template
sprint-task Task 3 [project:PROJ] Project-specific task

When applying a template, atlcli searches in order:

  1. Project level (.atlcli/templates/jira/)
  2. Profile level (~/.atlcli/profiles/<name>/templates/jira/)
  3. Global level (~/.atlcli/templates/jira/)

The first match wins, allowing project-specific overrides of global templates.

Templates capture:

  • Issue type
  • Summary (as pattern)
  • Description
  • Priority (by ID)
  • Labels
  • Components
  • Fix versions
  • Custom fields

Templates never capture project, assignee, status, or system fields.

Jira and Confluence are trademarks of Atlassian Corporation Plc. atlcli is not affiliated with, endorsed by, or sponsored by Atlassian.