Jira Ticket Templates

Epic

Use this template for large features or initiatives that span multiple sprints.

## Motivation

*What is the motivation for this epic? Why is this epic important?*

## Goal

*The primary objective or outcome that the epic aims to achieve.*

## Scope

*The scope of the epic, including the features, functionalities, and business requirements that are included.*

## Dependencies

*List of dependencies that the epic has on other projects, teams, or systems.*

## Risks and Challenges

*List of potential risks, challenges, or obstacles that may arise during the execution of the epic.*

## Stakeholders

*List of key stakeholders who are involved in the epic, including customers, users, and internal teams.*

- Responsible:
- Accountable:
- Consulted:
- Informed:

## Timeline

*The estimated timeline for the epic, including any milestones or deliverables.*

## Acceptance Criteria

*The acceptance criteria that must be met for the epic to be considered complete.*

## Metrics & KPIs

*The metrics that will be used to measure the success of the epic, such as customer satisfaction, revenue, or user engagement.*

Improvement

Use this template for improvements to already existing functionalities.

## General Description

*General description as a direct paragraph in the "Description" section.*

## Current Solution

*Description of the current solution and a short explanation why it should be improved.*

### Screenshot of the current element / design

*A screenshot should also be added here, which helps to identify the right place!*

## Desired Improvement

*Description of the desired improvement and a short explanation why this improvement is desired or what the advantage is.*

### Mockup of the desired change / design

*A mockup of the desired version and makes it clear what goal is to be achieved.*

## Acceptance Criteria

1. First acceptance criteria
2. More acceptance criteria

Design Task

Use this template for design-related tasks that require mockups, wireframes, or graphical assets.

## Motivation

*What is the motivation for this design task?*

## Additional Information

*Additional information that explains the exact circumstances of the feature in more detail.*

## Acceptance Criteria

1. First acceptance criteria
2. More acceptance criteria

## Definition of Done

- Design mockups have been created
- Design meets usability standards
- Design has been reviewed and approved
- Design has been tested
- Documentation has been created
- Design has been signed off

## Contacts

- Requirements: @Name
- Design: @Name
- Development: @Name
- Business Analyst: @Name

## Mockup / Wireframe / Graphical Assets

- Link to design:
- Link to other resources:

Bug

Use this template for bugs, programming errors, presentation errors, or functional errors.

## General Description

*General description as a direct paragraph in the "Description" section.*

## Steps to Reproduce

1. Step #1
2. Step #2
3. Step #3

## Observed Behavior

*Short description of the detected behavior incl. screenshot.*

## Expected Behavior

*Short description of the expected behavior incl. screenshot.*

## Implementation Notes (optional)

*A short specification or notes which may be relevant or helpful for fixing the bug.*

### Environment

- Operating System:
- Browser:
- Date & Time: