mode: ‘ask’

I am going to copy you a jira template, and I will be copying to you a bunch of discussions and context after that, can you help me make the jira issue and provide a title for it?

IMPORTANT, make sure to follow these guidelines:

• Make sure to don’t add implementation details, just the high level context. We want to keep the implementation details for the engineers to figure.
• Try to add link if you see something that can be linked in the jira issue.
• Always output as Jira markdown formatting.
• Make it easy to copy and paste to the jira input box.
• Do not mention customer names. Just reference them as “customer”.

Assistant instructions (use this when I paste template + context)

• I will paste a Jira template followed by discussion/context. Produce:
  • A concise Jira issue body that fills the provided template (Jira markdown).
  • A short, descriptive issue title (one line).
• Keep the issue high-level — do NOT add implementation details or design steps. Engineers will own those.
• Prefer including links when available (use full URLs or JIRA-KEY format).
• Use clear, testable Acceptance Criteria (Given / When / Then or numbered checklist).
• Always add blockquote jira-markup at the start and finish at the start and end of the output.
• Output only Jira-compatible markdown (no code fences or extra commentary) and format so it’s copy-paste ready into the Jira input box.

Jira Template

h1. Story (Required)

As a <PERSONA> trying to <ACTION> I want <THIS OUTCOME>

_<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>_

h2. *Background (Required)*

_<Describes the context or background related to this story>_

h2. *Out of scope*

_<Defines what is not included in this story>_

h2. *Approach (Required)*

_<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>_

h2. *Dependencies*

_<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>_

h2. *Acceptance Criteria  (Mandatory)*

_<Describe edge cases to consider when implementing the story and defining tests>_
_<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>_

h1. *INVEST Checklist*

 Dependencies identified

 Blockers noted and expected delivery timelines set

 Design is implementable

 Acceptance criteria agreed upon

 Story estimated