Easy Issue Templates for Jira helps teams turn repeated Jira work into reusable templates: simple bug reports, user stories, tasks, full Epic hierarchies, onboarding checklists, service requests, and more. Instead of rebuilding the same issue structure every time, users can choose a template, fill only the values that change, and create consistent Jira issues faster.
Use templates to standardize issue content, prefill supported Jira fields, create child issues and subtasks, collect dynamic values with variables, and trigger issue creation from Jira Automation or external tools.
How teams use Easy Issue Templates
Most use cases fit into one of two patterns:
-
📋 Flat templates for one issue at a time: bug reports, user stories, tasks, helpdesk requests, purchase requests, and test cases.
-
:card_index_dividers: Structured hierarchy templates for repeatable work that needs a parent issue plus child issues or subtasks: Epics, onboarding, offboarding, release plans, implementation projects, and ITSM processes.
Templates can include prefilled Summary, Description, Priority, Labels, Assignee, supported custom fields, and other supported Jira fields. For dynamic details, use variables such as <<Customer name>>, <<Start date>>, <<Environment>>, or <<Affected module>>.
Issue creation options
|
Flow |
Best for |
What users get |
|---|---|---|
|
Jira Create Issue screen |
Fast creation of flat or lightweight templates directly from Jira’s native Create screen. |
Users select a template from the Create screen, or a default template can auto-prefill fields based on project and issue type. Variables and template structure can also be handled when available for the selected template. |
|
Easy Templates Create flow |
Creating complete issue sets from structured templates. |
Users choose a template, review the structure, fill variables, and create the parent issue with selected child issues or subtasks in one flow. |
|
Easy Templates Prefill flow |
Cases where users want to review or adjust fields before final creation. |
The template opens Jira’s Create Issue screen with fields prefilled, so the user can edit details before clicking Create. |
|
Automation and REST API |
Recurring work, event-based creation, and integrations with external systems. |
Jira Automation or another system sends a web request to create issues from a template or apply a template to an existing issue. |
More on Using Templates: Using Templates
Software delivery templates
🐛 Bug report template
Use when: teams need consistent, complete bug reports without reminding reporters what to include.
Template may include:
-
Steps to reproduce
-
Actual result and expected result
-
Environment, browser, platform, app version, affected module
-
Severity, priority, component, labels, assignee, and other supported fields
Variables to consider: <<Platform>>, <<Browser>>, <<Software version>>, <<Module>>, <<Steps to reproduce>>.
Summary: <<Short bug summary>>
Steps to reproduce
1. <<First step>>
2. <<Second step>>
3. <<Third step>>
Actual result
<<What happened>>
Expected result
<<What should happen>>
Environment
Platform: <<Platform>>
Browser: <<Browser>>
Version: <<Software version>>
Module: <<Module>>
Recommended flow: Jira Create Issue screen for everyday bug reports; Automation when bugs should trigger predefined QA subtasks.
📝 User story template
Use when: product and engineering teams need stories that consistently describe the user, goal, and acceptance criteria.
Template may include:
As a <<User type>>
I want to <<Action>>
So that <<Goal>>
Acceptance criteria
Given <<Context>>
When <<Action>>
Then <<Expected result>>
Recommended flow: Jira Create Issue screen for simple stories; Prefill flow when the author should adjust details before submission.
🎯 Epic template
Use when: a team repeats the same project, feature, implementation, migration, or rollout structure.
Template may include a hierarchy such as:
-
Epic:
<<Feature or project name>>-
Story: Discovery and requirements
-
Subtask: Confirm stakeholders
-
Subtask: Define acceptance criteria
-
-
Story: Implementation
-
Subtask: Backend changes
-
Subtask: Frontend changes
-
Subtask: Documentation update
-
-
Story: QA and release
-
Subtask: Test plan
-
Subtask: Regression testing
-
Subtask: Release notes
-
-
Recommended flow: Easy Templates Create flow for full hierarchy creation, or Jira Create Issue screen when users need template selection inside the native Create screen.
✅ Task template
Use when: teams create recurring standalone work with the same fields and instructions.
Examples: content update, release checklist item, access review, compliance check, reporting task, environment maintenance.
Recommended flow: Jira Create Issue screen with an optional default template per project and issue type.
☑️ Test cases
Use when: QA teams need repeatable testing structure and clear expected results.
Template may include:
-
Preconditions
-
Test data
-
Steps
-
Expected result
-
Environment
-
Regression scope
Test case: <<Feature or scenario>>
Preconditions
- <<Required state, account, or setup>>
Test data
- <<User, item, file, or input data>>
Steps
1. <<Action>>
2. <<Action>>
3. <<Action>>
Expected result
<<Expected result>>
Regression scope
<<Areas to re-check>>
Recommended flow: flat template for a single test case, or hierarchy template to create a test plan with multiple test tasks and subtasks.
Business and HR templates
👥 Employee onboarding template
Use when: HR, IT, Security, Facilities, and managers need a repeatable new-hire process.
Typical hierarchy:
-
Epic or Task: Onboard
<<Employee name>>-
Task: Prepare contract and HR documents
-
Task: Create accounts and permissions
-
Subtask: Email and identity provider access
-
Subtask: Jira, Confluence, Slack, or other tools
-
-
Task: Prepare hardware
-
Task: Workspace and first-day plan
-
Task: Manager onboarding checklist
-
Epic or Task: Onboard <<Employee name>>
Variables
Employee name: <<Employee name>>
Job title: <<Job title>>
Department: <<Department>>
Manager: <<Manager>>
Start date: <<Start date>>
Location: <<Location>>
Tasks
- Prepare contract and HR documents
- Create accounts and permissions
- Email and identity provider access
- Jira, Confluence, Slack, or other tools
- Prepare hardware
- Workspace and first-day plan
- Manager onboarding checklist
Variables to consider: <<Employee name>>, <<Job title>>, <<Department>>, <<Manager>>, <<Start date>>, <<Location>>.
Recommended flow: Easy Templates Create flow for manual onboarding, or Automation and REST API when onboarding should start from a JSM request, HRIS, recruitment, or another external system.
:closed_lock_with_key: Employee offboarding template
Use when: a company needs a controlled, auditable offboarding checklist.
Typical hierarchy:
-
Task: Offboard
<<Employee name>>-
Task: Disable accounts and revoke access
-
Task: Collect hardware
-
Task: Transfer ownership of Jira issues, documents, and assets
-
Task: Final HR and payroll steps
-
Recommended flow: structured template with required variables and automation for time-sensitive access removal.
💰 Purchase request template
Use when: finance, procurement, or operations teams need standardized purchase requests.
Template may include:
-
Requested item or service
-
Business justification
-
Cost center or department
-
Budget owner
-
Vendor, estimated amount, required date
-
Approval checklist or subtasks
Recommended flow: Jira Create Issue screen for a single request, or Automation when requests should be generated on a schedule or from another business system.
JSM, ITSM, and helpdesk templates
🛠️ JSM and ITSM requests
Use when: service teams need consistent internal work after a request is raised.
Easy Issue Templates can help service teams create agent-side issue structures for incidents, service requests, access requests, onboarding, asset changes, or operational checklists. For example, a JSM request can trigger a template that creates the required IT, Security, and Facilities tasks in the right Jira project.
Recommended flow: Automation and REST API for requests raised from Jira Service Management; Easy Templates Create flow for agent-driven work creation.
🛟 Helpdesk requests
Use when: support agents repeatedly create the same follow-up tasks.
Examples:
-
Access request checklist
-
Device replacement
-
Software installation
-
Account recovery
-
Incident follow-up subtasks
Recommended flow: Apply a template to an existing issue with automation, or use a predefined template from the app flow when agents need to choose the right checklist manually.
▶️ Automation examples
Automation is useful when templates should run without users manually selecting them every time.
-
Scheduled recurring work: create monthly finance, compliance, maintenance, or reporting tasks.
-
Transition-based work: when a story moves to QA, apply a QA checklist or create testing subtasks.
-
JSM-triggered work: when a service desk ticket is created, generate a related onboarding, access, or ITSM task structure.
-
External systems: when an HRIS, CRM, ERP, or recruitment tool sends a webhook, create Jira issues from a template with variables mapped from the external payload.
Choosing the right template type
|
Need |
Use |
Examples |
|---|---|---|
|
One issue with standard text and fields |
📋 Flat template |
🐛 Bug report, 📝 user story, ✅ task, :headphones: helpdesk request, :shopping_trolley: purchase request |
|
Parent issue with child issues or subtasks |
:card_index_dividers: Hierarchy template |
🎯 Epic, 👥 onboarding, :closed_lock_with_key: offboarding, :test_tube: test plan, implementation project |
|
User must enter values during creation |
:pencil2: Template variables |
Employee name, start date, customer name, environment, module, due date |
|
Template should appear in Jira’s native Create screen |
:window: Jira Create Issue screen integration |
🐛 Bug report, 📝 story, ✅ task, default template per issue type |
|
Template should run automatically |
⚙️ Automation or REST API |
Scheduled tasks, JSM-triggered work, onboarding from external systems |
More template ideas
Related documentation
-
Use Jira native Create Issue Screen integration
https://help.appliger.com/easy-templates-for-jira/use-jira-native-create-issue-screen-integration -
Use Easy Templates app's Screen flow
https://help.appliger.com/easy-templates-for-jira/use-easy-templates-app-s-screen-flow -
Automation & REST API
https://help.appliger.com/easy-templates-for-jira/automation-rest-api
Have an idea or use case to share?
We’re always looking for new template ideas and workflow examples that can help teams get more value from Easy Issue Templates for Jira. If you have a feature request, improvement suggestion, or a use case you would like us to cover, submit it on our public Canny board.
https://appliger.canny.io/feature-requests-easy-templates
For any questions or feature requests contact us via Customer Portal