Jira issue templates are the answers for efficient workflow and improvement Jira project management.

Do you want to simplify creating repetitive issues? Is standardized Jira tickets your dream? Are you suffering from clutter and inconsistency in your Jira issues? With Jira issue templates you keep your issues clean and simple.

All you need to do is for the Jira administrator to create a ticket template and each Jira user will be able to use it when creating a new issue.

For what type of issue type can you create a template?

Choose your fighter! You can create:

• 🟣 epic template

• 🟢 story template

• 🔵 tasks template

• 🟡 subtask template

and all issue types that are defined within the project.

Which Jira projects are supported?

At this moment, you can crate Jira ticket templates for :

• company-managed software projects

• company-managed business projects

💖 Why people love and use issue templates?

• Read more how different project teams use our app and how they benefits from it.

• Meet Macopedia and their Success Story: how they saved hours thanks to Issue Templates Agent.

Only three steps are away from improving Jira ticket creation:

1. Create a template in the template library.

2. Use the template when creating a new Jira issue with subtasks, epic or story.

3. Enjoy the order and consistency of Jira tickets, as well as the time saved. Users no longer have to wonder "How to complete this issue?" 🎉

Creating Jira issue templates speeds up and organizes the work of people who play different roles in the team. Below you will find some templates that can inspire you to create your own templates for your company's processes:

• User story template for product owners

• Test plan template for testers

• Bug template for testers

• New employee onboarding template

• Employee offboarding template

• Helpdesk template

• Purchase request template

Benefits of using Jira issue templates in your team:

Consistency and Standardization: Issue templates ensure that every new task or project follows a standardized format. This consistency helps in creating a clear and uniform structure for different types of issues.

Time Savings: By providing predefined templates, Jira reduces the time spent on creating issues from scratch.

Reduced Errors and Miscommunication: Jira issue templates help in preventing common errors and miscommunication by guiding users to include essential information. This reduces the likelihood of missing critical details and ensures that everyone involved in the project is on the same page.

Improved Collaboration: Clear and well-structured Jira templates enhance collaboration among team members.

Issue Templates Agent app is an application that allows you to apply issue templates unhindered and extremely fast.

Our ticket templates are implemented right away on the issue create view, and you don't need any additional projects for that.

🔑 What are the key features of Issue Templates Agent?

1. Create templates – create ticket templates of any issue type that is assigned to project. Create many pairs for project and issue type and pre-define fields to improve workflow and speed up issue creation.

2. Hierarchies – create epics with already prefilled child tasks. Add templates of tasks, stories, or other issue types and then subtemplates. Up to 3 levels: epic/task (other issue type)/subtask.

3. Templates library – manage all the templates at one place. Filter them, categorize it, delete or edit whenever you need. Give special app permissions for your team if you want.

4. Use the template on the issue create view – apply ticket templates right away on the issue create screen. Choose which template you want to implement, and define fields with one click. Speed up issue creation and create data-completed tasks.

5. Multiproject and default – create issue templates for many pairs of project and issue types. You can assign one template to many projects and also set a default template. Then, the default template will be automatically applied on the create issue screen for each project.

6. Variables – use variables to customize your templates fully. It works on parent and child templates.

What is a test plan in software testing?

A test plan is a written document that describes the goals, methodology, and timetable of the planned testing operations. The resources required for the software tester to perform their job well may also be listed in the test plan.

Test plan Jira issue template

Create a test plan template that is quite complicated. Make sure your testing team and others work according to a pattern. Describe the test plan in the template, and don't miss any stage. Keep an eye on progress, and have one source of truth.

How to create the Test plan Jira issue template?

Feel free to copy our idea for this Jira issue template 🤗

Issue template name: Test plan

Issue type: Epic Summary: Test plan for … [title with version number]

Issue type: Task Summary: Create a test plan for […] Description:

Create a test plan for [title with version number].

Subtasks:

1. Analyze the app and identify which software features will be tested

Description:

• Clearly define the objectives of the test plan, such as ensuring the functionality, performance, and security of the web application.

• Define the scope by specifying the features, modules, or components that will be included in the testing.

1. Identify testing team

Description:

• Identify and assembly your team (everybody involved in the testing process including developers, testers, project managers etc.)

1. Gather requirements

Description:

• Collect and analyze the requirements of the web application to understand its functionality, features, and performance expectations

1. Establish test methodologies

Description:

• Develop a high-level test strategy that outlines the overall approach to testing, including test levels (unit testing, integration testing, system testing), test types (functional testing, performance testing, security testing), and the criteria for entry and exit

1. Specify test environment

Description:

• Identify the hardware, software, network configurations, and other prerequisites necessary for testing.

• Ensure that the test environment closely mirrors the production environment

1. Prepare testing schedule (start/end dates, who’s responsible)

Description:

• Create a detailed test execution plan that includes the schedule, resources, and responsibilities for executing the test cases.

• Define the test data required for each test case.

1. Prepare test cases

Description:

• Develop detailed test cases based on the gathered requirements. Test cases should cover functional aspects, performance metrics, and security measures.

• Organize test cases in a hierarchical structure with main test cases and related sub-test cases.

1. Plan for test execution

Description:

• Create a detailed test execution plan that includes the schedule, resources, and responsibilities for executing the test cases.

1. Define the defect management process

Description:

• Define the process for logging, tracking, and managing defects.

• Establish criteria for severity and priority, and set up a process for retesting and validating fixes.

Issue type: Task Summary: Test execution Description:

Execute the test cases according to the test execution plan. Record the results, including pass/fail status and any deviations from expected outcomes.Subtasks examples:

• Execute Functional Tests

• Execute Security Tests

• Execute Performance Tests

Issue type: Task Summary: Prepare test summary report Description:

Summarize the results of the testing phase, including test coverage, defect metrics, and overall assessment of the web application's quality. Provide recommendations for improvements if necessary.

Issue type: Task Summary: Testing process review Description:

Conduct a review of the test plan with key stakeholders and obtain their approval. This ensures that everyone is aligned with the testing strategy and objectives.Subtasks:

• Evaluate the accuracy and completeness of test summary reports

Assess the inclusion of key metrics and KPIs

If you want to create such a table then just type the command /table 😊

🔑 What are the key benefits of using Jira issue templates in Atlassian project management?

1. Time savings – think about how many Jira issues your team creates daily. With issue templates, you can speed up issue creations that are repetitive or demand lots of typing. In a month, you save even hours of your teams' time and implement efficient Atlassian project management.

2. Reduced errors – if you predefine what details you need in tickets, you get well-constructed issues with all crucial data. With already prepared structure templates, you minimize the chances of errors that may occur when manually configuring projects or issues.

3. Issues standardization – issue templates facilitate standardization of best practices and procedures across different projects or teams, promoting a unified approach to project management.

4. Consistency – ticket templates ensure consistency in project workflows, issues, and documentation by providing predefined templates. This helps standardize processes across teams and projects.

5. Reusability – you can use one template all over again with many projects. Teams can capture the best practices from previous projects and apply them to new ones by using templates, fostering continuous improvement.

6. Customization – You can easily edit Jira issue templates and make adjustments when applying them on the issue create screen.

With Issue Templates Agent for Jira, you can do even more!

🚀 Main advantages of Issue Templates Agent for Jira:

• Immediately apply templates on the create issue screen: Don’t start from scratch every single time. Speed up creating Jira tickets with ready-to-use templates. Use them once you open the perfectly familiar to you, native Jira Create issue screen and fulfill fields automatically. Use epic templates, Jira task templates, and story templates - all with subtasks.

• Create your own tailor-made Jira issue templates: Make and save issue templates in the template library. One storage place means transparency and easy global configuration for admin. Take over control, speed up the creation of issues by your team, and enjoy standardized Jira tickets.

• Multiple issue templates per project: Template can be matched with many issue types. You can create multiple templates with different sets of issue types and for which issue type the template should be defaulted to improve Issue creation, specify in which project it can be available. Templates setup is hassle-free, no matter how many templates you as an admin need to prepare.

What is a user story?

A user story is nothing else than a written explanation of a software feature but from the perspective of its user. Each feature or product should bring value to end users, and we can check if values appear with user stories.

Ready-to-use user story Jira issue template

Use one template across many project and work with a pattern. Provide all relevant data in every issue and speed up teams' performance. Create one Jira issue template that will reflect end user thinking.

How to create user story Jira issue template?

Fell free to copy our idea for this issue template 🤗

Template name: User story

Summary: User story [product/feature]

Template body:

Background:

[Describe here]

Acceptance criteria:

[Describe here]

Any other details:

[Describe here]

What is the employee onboarding process in HR?

Employee onboarding is a crucial process in Human Resources (HR) that focuses on integrating new employees into an organization. It includes the steps and activities designed to help newcomers become familiar with their roles, the company culture, and the overall work environment.

Employee onboarding Jira issue templates for HR projects

This template is perfect for HR teams, but it also can be assigned for any project where a new employee is going to appear. You can customize the description when you need and enjoy standardized processes. Create a comprehensive onboarding process with one issue template, and don't miss anything.

How to create an employee onboarding Jira issue template?

Feel free to copy our idea for this issue template 🤗

Template name: Employee onboarding

Epic: Onboarding [name of new hire/department]

Description: Create a comprehensive plan for onboarding a new team member.

Tasks:

1. Prepare Onboarding Materials

Description: Description: Ensure all needed contracts are ready for the first day.

Subtasks:

• Sign an employment contract

• Create a welcome package with company swag

2. Set Up Equipment and Workspace

Description: Prepare hardware and software.

Subtasks:

• Order necessary equipment (laptop, phone, etc.).

• Prepare the workstation with essential tools and resources.

• Set up email accounts, and access to internal systems

1. Schedule Onboarding Sessions

Description: Prepare the agenda for the meeting with the team.

Subtasks:

• Create weekly meeting plan

• Send out calendar invites to new employees and involved parties.

1. Orientation phase

Description: Take care of proper company introduction.

• Prepare presentation slides for HR orientation.

• Prepare a Confluence page with information on company policies, structure and benefits, and enrollment process.

1. Training phase

Description: Prepare training sessions and assign a mentor.

• Gather training knowledge base

• Assign a coordinator

1. Assign Onboarding Buddy

Description: Pair the new employee with a seasoned team member to assist with integration and answer questions. Establish regular check-ins for the first few weeks.

What is a bug in Software?

A bug in a Software environment is an unexpected disruption of software or hardware. According to Atlassian a bug is a problem which impairs or prevents the functions of a product.

Reporting a bug Jira issue template

Make sure your developers get all relevant information to eliminate the bug. Use templates to provide standardized issues, and save your team's time on looking for patterns in previous tasks. Thanks to read-to-use Jira issue template, everyone who wants to report a bug, knows exactly what to put into an issue to provide all of relevant details.

How to report a bug Jira issue template?

Fell free to copy our idea for this issue template 🤗

Template name: Bug reporting

Summary: Bug reporting of [name the software]

Template body:

Description:

[Text]

Steps:

1. [Text]

Actual results:

[Describe them here ]

Expected results:

[Describe them here ]

Screenshot:

[insert screenshot]

What is a Helpdesk team in IT company?

A Helpdesk team in an IT company is a group of IT knowledgeable people responsible for providing technical support and assistance within the organization. Helpdesk team ensures that computer systems, software applications, and other technology-related issues are taking care of.

Jira issue templates for reporting issues to the Helpdesk

Speed up Helpdesk issue resolution with well-crated Jira issues. Create a template to tell others what data should be insert in task, ans what information Helpdesk team needs to help you. This way your team mates will always know what information put into the Jira ticket to give all relevant data to the Helpdesk.

How to create Jira issue template for Helpdesk tickets?

Fell free to copy our idea for this issue template 🤗 This one is about reporting access requirement.

Template name: Access request

Summary: Access request

Template body:

Hello, please provide me an access to [fill with the name od Software].

Type of Access Requested: [bold the right one]

Full Access

Read-Only Access

Custom Access (Specify: ________)

Explain briefly why you need access to it and how it contributes to your role or project:

Write here

What is employee offboarding process?

People come, and go! Employee offboarding is a process of managing an employee's departure from your company. It involves many tasks and activities to ensure a smooth transition for both the departing employee and the organization. Despite appearances, offboarding process is as important as onboarding, because it shows company's relationships with others.

Employee offboarding Jira issue templates for HR projects

Create a template with full list of to do's and make sure HR team won't forget about anything during offboarding process. It can be also shared with many projects, so whenever there is a change in personnel, the template will be ready-to-use. Create one Jira issue template, and gain a ready-to-use, reliable checklist of tasks you should perform.

How to create employee onboarding Jira issue template?

Fell free to copy our idea for this issue template 🤗

Template name: Employee offboarding

Epic: Offboarding [name of departing employee/department]

Description: Develop a systematic approach for smoothly transitioning departing employees out of the company.

Tasks:

1. Exit Interview and Documentation

Description: Conduct an exit interview to gather feedback and complete the necessary paperwork.

Subtasks:

• Schedule exit interview with HR.

• Provide departing employees with necessary documents (exit checklist, non-disclosure agreements, etc.).

• Return of Company Property

1. Equipment

Description: Ensure all company-owned equipment and materials are returned.

Subtasks:

• Collect company laptop, phone, keys, access badges, and any other equipment.

• Confirm the return of all company-owned items and update inventory records.

1. Access Revocation

Description: Secure company data and systems by revoking access.

Subtasks:

• Disable access to accounts based on the onboarding checklist and later access request

• Revoke access to third-party platforms and accounts.

1. Knowledge Transfer and Documentation

Description: Document and transfer necessary knowledge and responsibilities.

Subtasks:

• Identify key tasks, projects, and responsibilities of the departing employee.

• Document processes and procedures that are specific to the departing employee's role.

• Assign a point of contact for any questions or support needed after departure.

1. Farewell Announcement and Transition Support

Description: Notify the team of the departure and facilitate a smooth transition.

Subtasks:

• Draft a farewell announcement email to be sent by HR or the departing employee.

• Coordinate handover of ongoing projects and responsibilities to other team members.

• Provide support to the team to ensure continuity and morale.

1. Offboarding Survey

Description: Gather feedback to improve the offboarding process.

Subtasks:

• Send out an offboarding survey to departing employees to collect feedback on their experience.

• Analyze survey responses and identify areas for improvement in the offboarding process.

• Implement any necessary changes based on feedback received.

Jira issue template glossary:

1. Jira issue template: a predefined structure for creating issues (tasks, stories, bugs, etc.) with consistent fields. Templates help standardize the information captured for different types of issues.

2. Issue Create View: in the context of project management or issue tracking systems, the issue Create view refers to the interface or page where users can input information to create a new task, problem, or any other unit of work that needs to be addressed within a project. To create an issue, click Create in the top navigation.

3. Template Library: a collection or repository of pre-designed templates that can be reused across various projects. A template library streamlines the process of creating consistent and standardized documents, designs, or structures.

4. Category: a label that you can assign to your templates for easier filtering. This feature is made only for managing templates and is visible only in the template library. The end user can't see it.

5. Multiproject templates: relating to or involving multiple projects. You can assign one template to multiple pairs: project and issue type.

6. Issue Type: in project management, an issue type refers to a distinct category or classification assigned to different types of tasks, problems, or work items. Common examples include bugs, tasks, and user stories.

7. Epic: in agile project management, an epic is a large and high-level body of work that is broken down into smaller, more manageable tasks or user stories. Epics typically represent major features or themes within a project.

8. Story: in agile development, a user story is a concise description of a desired feature or functionality from an end user's perspective. It serves as a way to express requirements in a user-centric manner, facilitating communication between development teams and stakeholders.

9. Subtask: a smaller, more specific unit of work that contributes to the completion of a larger task or issue. Subtasks are often used to break down complex tasks into manageable parts for better tracking and management.

10. Parent template: the main template that is applied on the Create Issue screen.

11. Child template: a template used to create an automatic whole structure, for which the use of a "parent template" is a trigger, such as a list of subtasks.

12. Default template: a template that is saved as default for a partial pair of a project and an issue type. It's automatically applied on the Create Issue screen when a user enters this project.

13. Variables: variables are symbolic names or placeholders used to represent and store data values. They are used to manipulating and storing information, creating issues and scheduling them.

14. Jira admin: a Jira Administrator, often referred to as Jira Admin, is an individual responsible for the configuration, customization, and overall administration of a Jira instance. This role involves managing user permissions, workflows, schemes, and configurations to ensure the effective use of Jira within an organization.

15. Bug report template: standardized issue format to systematically capture and communicate information about bugs identified during testing or usage. It typically includes specific sections for details such as the bug's description, steps to reproduce, expected behavior, actual behavior, severity, and any supporting files or screenshots.

16. Jira story template: a predefined structure designed to create user stories within Jira project management. User stories, commonly used in agile development, clearly describe a feature or functionality from an end user's perspective.

With the help of the Issue Templates Agent, you can speed up Jira issue creation and improve your Atlassian project management. Save your team's time, and make them avoid creating the same issues all over again.

How to install Issue Templates Agent?

Find Issue Templates Agent on the Atlassian Marketplace, or use Explore new apps under the Apps in Jira top navigation.

Install the app on your instance and then open it with Manage apps, choosing it on the right sidebar.

All templates are configured and managed in the global configuration.

How to access app configuration?

🐾 Steps

To find the page with app configuration:

1. Log in to your Jira instance.

2. Click Apps in the top navigation.

3. Select Issue Templates Agent.

Now, let's create your first template ⭐️

If you prefer to watch not to read, enojoy a demo video 👇

All templates are configured and managed in the global configuration.

How to access app configuration?

Steps

To find the page with app configuration:

1. Log in to your Jira instance.

2. Click Apps in the top navigation.

3. Select Issue Templates Agent.

Result 🎉

You’re on the page with app configuration. Let’s create your first template 👇

Create templates

If you need inspiration on what tasks can be a template, check out the page in our documentation.

Interactive demo on how to create a basic template 👀

🐾 Steps

To create a template:

1. Click Create template.

1. Then, decide which template you need: basic, simple, or advanced.

Basic: you can choose one issue type from all levels (1 -epics, 0 -tasks/stories/bugs, -1 -subtasks). You create one issue.

Simple: you can choose issue types from 0 and then -1 levels. Create a structure with 2 levels.

Advanced: by default, the first level is epic, and then you can create whole 3-level hierarchies.

1. On the first page, you can select:

• Name - Name of the template (It's a necessary field).

• Project(s) - The template will be used in projects (you can create one template for multiple projects). Only supported projects will be displayed: software and business company-managed projects.

• Issue type(s) - Issue types match the ones selected in the Project.

• Category - A label that will help you easily navigate through the template list to find the exact Template you are looking for.

• Set this template as default for issue types - with this setting, any time you select Issue Type in which template was set as default, the template will be applied immediately.

• Enabled / Disabled – decide if you want to let your team use this template or if it is only a draft. If you disable the template, it won't show up to choose on the crate issue view.

• Save the template.

💡 Add more fields you need, and define all the data to prefill with templates. You can find a full list of them on this page: Supported fields.

Result

You’ve created a template. Now your users can apply them to their issues and speed up issue creation 🎉

What is request management?

Request management is the process of receiving, monitoring, and resolving requests for access or services inside your company. Typically, it is the submission, a methodical tracking system, and an organised procedure for managing and completing such requests. This procedure keeps track of the requests and their progress.

Ready-to-use Purchase Request Jira issue template

This template is worth assigning to many project. Add fields that are needed to locate the person, such as office, department, reporter. Let everyone create a uniform shuffle, with all the necessary information to complete the order and deliver, for example, a laptop.

How to create purchase request Jira issue template?

Fell free to copy our idea for this issue template 🤗

Template name: Purchase Request

Summary: Purchase request

Template body:

Requesting order:

Link: insert link here

Explain briefly why you need it:

Manager that approved your request:

Epic: a large body of work that can be broken down into smaller tasks or user stories. Epics are typically used to organize and manage complex projects or initiatives, serving as a high-level container for related work items. They help teams prioritize and track progress toward achieving overarching goals by providing a structured framework for planning, execution, and monitoring.

See yourself with an interactive demo

Create epic issue templates with subtasks

In advanced structure, issue template creation starts with epic. You have to crate only epic on create issue view to get tasks and subtasks under the epic on project board.

Create a parent template:

1. Name the template.

2. Choose project(s) and epic(s).

3. Set the pair(s) as default if you want.

4. Fill in the summary and additional fields you choose.

Create child templates: tasks and subtasks.

Let's go to the child templates tab, create a task/story/ other issue type configured as level 0 in Jira and assigned to the project, and then subtasks.

1. First, create a task or other issue type you have assigned to the project. You can choose all the Jira company-managed projects: business, software and service desk.

2. Define the summary and additional fields in the issue template.

3. Save it as a subtemplate.

How to create an issue template with subtasks?

When you have already created a task/ story/ bug - a second-level issue template, it's time to add subtasks.

1. Expand the view of this child template and choose +Add subtemplate.

1. Choose subtasks as issue type.

2. Name the template and define the fields as usual.

3. Save as a subtemplate.

4. Create more subtasks - how many you need.

Result 🎉

You've just created an epic with tasks and subtasks from a template. It requires only epic creation, and the rest of the issues were created automatically.

A subtask is a more minor, specific component or part of a larger task or project. It is typically a task that must be completed to achieve the overall goal or objective. Subtasks help break down complex tasks into more manageable and actionable steps, allowing for better organization, delegation, and progress tracking.

The simple structure of issue templates allows you to create up to two levels in the hierarchy.

Here, you can start with a task, story, or bug - all issue types except epic, as a parent template. Then, create subtemplates. In the dropdown, we only have the Parent project option to choose from, as subtasks cannot exist as separate, detached issues – they must always have a parent from the current project.

Apply only the issue type you choose on the create issue view, and subtasks are automatically added under the parent issue.

Define all fields as usual, and go to the child templates to create subtasks.

Create as many subtasks as you need. Define summary and extra fields. Remember that the summary field is required in Jira, and so is here. Save the template as a subtemplate and enjoy the creation of subtasks automatically.

The subtasks creation order can be changed with drag and drop on the left.

The result 🎉

You've just created a task with subtasks—but only with a few clicks. The subtasks loaded automatically under the parent issue.

Use Templates in Automation

This feature allows you to automate many things, connected to creating standard issues that normally are boring and time-consuming. With Automation and Issue Templates Agent things like: Preparing Onboarding epic, or creation of project with prepared issues are now possible in a blink of an eye!

Check out our suggestions of use cases:

• Apply Template on existing Issue

• Create Issues with structure from Template

• Create new projects with issues

• Schedule Issue Creation

Everything you need to your automation rule

1. API Token

2. REST API url

3. Body of request (in case you would like to create a new issue, you need to add issueTypeId, to your own)

How to generate a token for automation rules?

These steps are required also in the Use cases in the subpages, so be sure to read it.

1. Go to Apps -> Issue Templates Agent -> Templates and select checkboxes near templates, you would like to use.

2. Press "Use in REST API".

3. Create some label for token and generate it.

If you already created a ticket template, let's use it to create a Jira issue. Let's improve your workflow and project management and save time! 💪

👀 See an interactive demo on how to create a simple template with 2-level hierarchy

How to create a Jira issue with the issue template?

Issue templates can be used directly on the Create issue screen during issue creation.

This way, it's superbly fast to implement the template you need and use it on the issue.💨

You can create a template for each issue type assigned to a particular issue project.

🐾 Steps to use template on the create issue screen

To use a ticket template:

1. Click Create in the top Jira navigation (as you want to create a regular issue).

2. Click in the template field and select a template from the list.

3. Select the template you need. Change the issue type if you have to, and then the templates selected will adjust.

4. After selecting the issue template, fields will be filled automatically with data provided in the template.

5. If you choose a simple or advanced structure that expands more than one issue, remember to create only the parent issue. Child templates will be created automatically.

6. If you created a default template for a pair: project and issue type, after switching to that issue type, the issue template will be automatically selected and implemented.

Results ✅

1. After selecting the issue template, fields that were added to the template will appear on the Create issue screen.

2. You can always change the template body and make your adjustments. Any value in fields is editable even after selecting Template. Remember to click Create to save your issue.

3. You can't change the kind of structure after selecting it.

Description

For many companies creating an issue is just a tip of an iceberg. They need to create subtasks, assignee etc. Let's do it with Automation and Issue Templates Agent

How to set up

2. Create new automation rule.

3. As a trigger select manual Trigger.

4. Add "send web request" and paste your API Token, and REST API url.

5. In web request body use "If you want to apply on existing issue".

6. Turn on the rule.

Results

Description

Let's say every new Team needs to have their projects, but all of them have something in common (like Welcome Issue, some epic etc). You can design Templates for that issues and apply it to a new Project, whenever it is created!

How to set up

1. Proceed steps mentioned here. (Remember to select Global Automation, that could be find in cog icon -> System)

2. As a Trigger select "When project is created".

3. Change web request body to custom Data and paste "If you want to create a new issue"

4. In the "issueTypeId" row, replace it with proper issue type. How to search for issue type?

5. Turn on the rule.

Results

Congrats! Whenever you will create a new project, issues will be automatically created inside it.

Description

In some cases, like Onboarding of new employee, you would like to create some group of Issues in many projects (like Time tracking issue, demo exercise, welcome Issue etc.)

How to set up

1. Prepare your template to be used in automation, like here.

2. Create new automation rule

3. As a Trigger select "Issue Created".

4. Add Issue field condition "Request type" equal "Onboarding".

5. Change web request body to custom Data and paste "If you want to create a new issue"

6. In the "issueTypeId" row, replace it with proper issue type, everywhere it's needed. How to search for issue type?

7. Turn on the rule.

Results

Congratulations! You can now create a "manager" issue and create structured issues without any additional actions.

You can create issues from the template in the issue view without changing the view. It is a massive facilitation during planning meetings and for all teams working with boards.

How to use issue templates on the issue view?

When the simplified task creation panel is displayed, it does not show the create issue view, only the summary bar, then the workaround is required. This applies to the issue view: epics to add childs / tasks to create subtasks etc.

It is then necessary for the Create issue dialogue to open up - this can be done by setting a minimum of one required field on Create issue (it can be a template field, but it does not have to). This way, templates can still be used to create an issue, not just by clicking the Create button from the top navigation bar.

Result 🎉

Creating tasks from the issue view and using issue templates speed up planning and adding tasks on the board.

Description

Sometimes you need periodically created issues where the only thing that changes is the date, for example. You can do this with the automation and Issue Templates Agent.

How to set up

1. Prepare your template to be used in automation, like here.

2. Create new automation rule.

3. As a Trigger select Scheduled and config everything as you wish.

4. Change web request body to custom Data and paste "If you want to create a new issue".

5. In the issueTypeId row, replace it with proper issue type. How to search for issue type?

6. Turn on the rule.

Results

Congrats! Your Issue is scheduled to be automatically created.

Whether you're a project lead or a team member, understanding these permissions is key to shaping issue templates and boosting your Atlassian project management.

Which permissions do you need to manage the Issue Templates library?

1. You have to be a Jira Administrator with global permissions.

2. You can share permissions with other Jira users. Go to Manage app, find Issue Templates Agent, and go to App setting (on the left sidebar).

3. You are transferred to the Jira permission page. Now, find Issue Templates Agent - Manage templates, and manage it like others permissions.

Remember, to grant permission only for users, you need to evaluate it from time to time to keep it clean and updated.

Create different templates for as many projects and issue types as needed.

If you know that a new procedure is coming, and the template will be a good option, stay ahead and prepare it early to be ready on the implementation day.

Save Jira issue template as a draft

If you don't want to share the template with your team yet, you can simply exclude them from templates available on the issue create screen.

1. Create a template, as always.

2. Disable the template with a toggle on the upper bar.

3. Save as always.

4. When the template is ready for publishing, turn on the toggle. The state of this toggle can be changed at any time and results in the absence of this template to select in the Template selector on the Create issue screen.

All created templates are visible in the table called Template Library. Below, you can find a description of each column.

Edit a template

You can easily edit each template. Just click on its name or click on three dots on the right and select Edit template. A drawer then opens where you can change the configuration. This action does not affect issues already existing in Jira.

Delete a template

You can delete a template by clicking the three dots icon in the last column and selecting Delete template. After clicking, a popup appears where you must confirm the deletion. This action does not affect issues already existing in Jira.

We listed practices you should follow to ensure your Jira ticket template library stays clean and transparent, and issue templates simplify your workflow.

1. Define clear templates – Clearly define and create templates for common types of issues or projects in your organization. Templates should include necessary fields. Make sure to add all specific information relevant to the issue or project type.

2. Standardized naming convention – Use standardized naming conventions for your templates to make it easy for Jira users to find and select the right template. Include a clear description in the issue template name to convey its purpose.

3. Include only relevant fields – Include only the necessary and relevant fields in your templates. Too many fields can be overwhelming and may lead to confusion.

4. Permissions and restrictions – Set appropriate permissions and restrictions on templates to control who can create or modify them. Ensure that only authorized users can modify or delete templates to maintain consistency.

5. Consider multiproject templates – Keep it simple. If you can, reuse templates for multiple projects instead of duplicating them.

6. Template Categories and Organization – Organize issue templates into categories based on project type, department, or any other relevant criteria. Make use of Jira's template categorization features to simplify template filtering.

7. Test Templates Before Deployment – Before making templates available to users, thoroughly test them to ensure they work as intended. Check for any issues with mandatory fields, and default values.

8. Version Control – If a lot of things change quickly in your organization, be sure to evaluate templates so that they are up to date.

Our list of supported fields grew significantly 🚀

✅ Supported system fields in creating Jira issue template

✅ Supported custom fields in creating Jira issue template

At this moment you can crate Jira ticket templates for:

• company-managed software projects

• company-managed business projects

We are committed to improving our security posture. That’s why we created this page to answer basic questions about security in the Issue Templates Agent app.

Since Oct 2023, we've been SOC2 type II compliant to meet the highest and most professional standards.

Issue Templates Agent Architecture

Issue Templates Agent is built on the Forge platform. The app connects to Jira using OAuth2. It’s written in React and TypeScript.

What customer data does the app process?

We process accountIds, email addresses, display name.

What data does the app store?

The app stores templates data.

Where are the data stored?

All data are stored on the Atlassian infrastructure. Templates data is stored in Jira (via UIM entities). The app configuration is stored via Forge Storage.

What permission does the app require?

Does the app encode all data in transit and at rest?

Yes.

Does the app support data residency?

Yes, thanks to using the Atlassian Forge platform. Here is the official announcement from Atlassian: https://www.atlassian.com/blog/developer/data-residency-is-coming-soon-in-beta-to-forge-hosted-storage-take-action-now-to-support-your-customers

Does the app have a data retention policy?

Yes. Upon written request, Appsvio and Atlassian will delete all End User Personal Data (including copies). More information is available in Forge DPA.

Does the app have a data backup policy?

Yes. More information is available in https://www.atlassian.com/trust/security/data-management

Useful links and more information

• Appsvio Trust Center

• Privacy Policy of Appsvio apps

Issue Templates Agent for Jira is constantly developed. We try to make all of your requests happen 😊

As of today (Jan 2024), we know several limitations related to this app.

• You can't use our app on the Customer Portal. We're waiting to add support for Jira Service Management.

• Templates can be configured and applied only for company-managed software and business projects.

• Support for Fix Version: If you have a version in the template which is archived, the Template can't be applied on the Create issue screen. You have to go to the template configuration and remove this version.

• Support for Component: If you have a component in the template which is removed from project, the Template can't be applied on the Create issue screen. You have to go to the template configuration and remove this component.

💡 Workaround for Parent field

Currently, the "Parent" field is not supported in the Create issue process from the template. Therefore, this field cannot be selected when configuring the Parent template.

Workaround: As a workaround, you can use an automation rule. After creating an issue, the rule can check the Template field and, depending on the configuration, trigger an edit of the Parent field on that issue, inserting the issue key of an existing task that is to be the parent.

The rule is configured as here:

This will work for both software and business projects.

Variables: placeholders that represent dynamic values used in various contexts, such as issues, workflows, automation rules, filters, and reports.

Customize your issue templates with variables. Thanks to this option, all your issues can be updated with the necessary variables.

Suppported variables

Currently, we support variables for text fields: Summary, Description, custom field paragraph (supports rich text), custom field short text (plain text only)

Result 🎉

1️⃣ step:

2️⃣ step: