UX Jira ticket Templates

Product Requirements Document Template - 2.0

Creating a well-structured template for product owners to fill out in Jira can significantly streamline the UX design process and ensure that
the UX team has all the necessary information.

User Story Template

Use Case: Use this template when you have a specific user action or task that needs to be implemented. It's ideal for breaking down a
user's needs into actionable items. This is also the ticket that represents the UX Process so we can have a deep understanding of how
complete an Epic is.
Why Choose It: Ticket creators may prefer this template when they have a clear understanding of a user's goal and need to translate it
into a development task. This can also be beneficial when needed to break down large features.
Problem Defined:
Solution
Hand Off

General User Story Template:

Title: [Concise title of the user story]

User Story: As a [user type], I want to [perform an action] so that I can [achieve a goal].

Acceptance Criteria:

@Erica.Price Define and ideal UX AC.

[Detailed acceptance criterion 1]
[Detailed acceptance criterion 2]
[Scenarios]
Positive
Negative
[Key tasks]
[Edge Cases - How often will this happen?]
What if

Context

Why does this ticket exist?

What is the problem?
Who asked for it?

Out of scope:

OOS for now

[Phase 2]
OOO forever
[Just NO]

UX Requirements:
 [List of specific UX-related requirements, e.g., wireframes, user flow diagrams, interactive prototypes, etc. Describe the problem and
not the solution.]

User Research Insights:

[Summarize any relevant user research findings]

Who signed off on this:

Admin dev:
API Dev:
UX:
PO:

Risk:[Is there any risk for this scope to change after ideation? Define those risks? Ex: Dev doesn’t know how it will work, will need to
spike. ]

Dependency: [On other teams? Context from other teams?]

Attachments: [Links to any related documents or assets]

PO Considerations:

Problem Defined

Problem - Intent

Is the problem for this epic clearly defined? Acceptance Criteria:

Summary of the problem:
Provide a concise summary of the problem that this epic aims to address.
PRD Attached:
Ensure that the Problem Requirements Document (PRD) is attached to the user story.
PRD clearly defines problems:
Verify that the PRD clearly articulates and outlines the identified problems.
Has the problem been vetted by the triad:
Confirm that the problem has been reviewed and approved by the triad (Product Manager, Developer, and UX Designer).
Send PRD to everyone before and ask everyone to bring questions. At the end, everyone should have a clear understanding on
what problem needs to solve.
UXer has a clear understanding of the background and context of the problem and feels confident in their ability to
solution:
Ensure the UX designer thoroughly understands the problem's context and feels confident in proposing a solution.

Optional AC:

Current implementation of the solve for problem analysis:

If applicable, provide insights into the current implementation of the solution analysis.
Usability testing:
Conduct usability testing to gather insights into the user experience with the proposed solution.
User observation and interview on the subject:
Engage with users through observation and interviews to gather additional insights.

Solution

Solution - Intent

Prescribe the solve of the problem Acceptance Criteria:

 Clear Problem Statement:
Clearly state the problem that the proposed solution aims to address.
Wireframes:
Provide detailed wireframes illustrating the proposed solution.
Approval by triad:
Ensure that the proposed solution has been reviewed and approved by the triad.

Optional AC:

Usability testing on the solution:

Conduct usability testing specifically focused on the proposed solution.
Workshops for idea generation:
Facilitate workshops to generate additional ideas and insights related to the proposed solution.

Hand off

Handoff - Intent

The solution has been defined clearly and can be handed off to the dev Acceptance Criteria:
Figma handoff file:
Provide a Figma handoff file that includes all necessary design assets and specifications.
Edge cases:
Clearly outline edge cases to ensure comprehensive understanding during development.
Happy paths:

Define the happy paths to guide developers through the primary user interactions.
Annotations:
Include annotations within the design files to provide context and details about specific design elements.

EPIC: Feature Request Template

Use Case: Use this template when you have an idea for a new feature or a significant enhancement to an existing feature. It's suitable
for proposing larger changes or additions to the product.
Why Choose It: Ticket creators might opt for this template when they want to provide a comprehensive overview of a feature idea,
including its potential benefits, user impact, and any high-level design concepts.

Feature Request Template

Title: [Descriptive title of the feature request]

Request Origin: [What person/ team/ user influenced this request]

Description:
[Provide a detailed description of the feature, its purpose, and its potential impact on users.]

User Pain Points:

[List any user pain points or challenges that this feature aims to address.]

UX Considerations:
[List specific UX considerations or challenges related to this feature]
[Include any design ideas or concepts]
[Include specific user interactions that need to be included in the final design]

Attachments: [Links to any wireframes, sketches, or related files]

Who signed off on this:

 Admin dev:
API Dev:
UX:
PO:

Risk:[Is there any risk for this scope to change after ideation? Define those risks? Ex: Dev doesn’t know how it will work, will need to
spike. ]

Dependency: [On other teams? Context from other teams?]

PO Considerations:

Feel free to use these questions as a starter for the document

What problem or need does this feature address for the users?
Who are the primary users who would benefit from this feature?
Are there any specific pain points or challenges that this feature aims to solve?
How would you measure the success of this feature?
Are there any technical constraints or dependencies for implementing this feature?
Have you considered how this feature fits into the overall user experience of the product?
Are there any design concepts or ideas that you'd like the UX team to explore?
What is the priority of this feature in relation to other product enhancements?

Bug Report Template:

Use Case: Use this template when you encounter an issue or bug in the product that needs to be fixed. It's essential for reporting and
tracking defects.
Why Choose It: Ticket creators should use this template when they come across unexpected behavior or issues within the product. It
helps the development team understand the problem, reproduce it, and prioritize fixes.

Bug Report Template:

Title: [Brief description of the bug]

Request Origin: [What person/ team/ user influenced this request]

Description:
[Provide a detailed description of the issue, including steps to reproduce, expected behavior, and actual behavior.]

Impact on User Experience:

[Explain how this bug affects the user experience and why it should be prioritized.]

Attachments: [Screenshots, videos, or logs that illustrate the issue]

Who signed off on this:

Admin dev:
API Dev:
UX:
PO:

Risk:[Is there any risk for this scope to change after ideation? Define those risks? Ex: Dev doesn’t know how it will work, will need to
spike. ]

PO Considerations:

What is the exact issue or bug you've encountered?

Can you provide a step-by-step description of how to reproduce the issue?
 What is the expected behavior, and what behavior did you observe?
Have you identified any potential root causes or troubleshooting steps?
How critical is this bug in terms of its impact on user experience?
Are there any specific user scenarios where this bug occurs?
Have you seen similar issues reported by other users or team members?
Can you attach any relevant screenshots or recordings of the bug?

Epic: Enhancement Request Template:

Use Case: Use this template when you have suggestions for improving existing features or making smaller, incremental changes to the
product.
Why Choose It: Ticket creators may prefer this template when they want to propose improvements that don't involve major new
features. It's a way to communicate ideas for enhancing the product's usability and performance.

Enhancement Request Template:

Title: [Descriptive title of the enhancement request]

Request Origin: [What person/ team/ user influenced this request]

Description:
[Explain the desired enhancement, including its purpose and potential benefits to users.]

Current Pain Points:

[List any current issues or limitations that this enhancement would address.]

UX Suggestions:
[Provide any UX-related suggestions, such as interface improvements, user flow optimizations, or usability enhancements.]

Attachments: [Links to any design mockups or sketches]

Who signed off on this:

Admin dev:
API Dev:
UX:
PO:

Risk:[Is there any risk for this scope to change after ideation? Define those risks? Ex: Dev doesn’t know how it will work, will need to
spike. ]

PO Considerations:

What is the specific enhancement you are requesting, and why is it needed?
Are there any existing pain points or limitations that this enhancement would address?
How would this enhancement improve the overall user experience?
Are there any design or user interface considerations related to this enhancement?
Are there any technical considerations or constraints to be aware of?
Do you have any specific expectations for the timeline or priority of this enhancement?
Have you discussed this enhancement with end-users or stakeholders for their input?
Can you provide any context or background information that might be useful for the UX team?