See a sample issue here

[he-james]

Title above should be: [Action verb (Create, Allow, Update)] a [Feature] (optional: in [(Primary) Repo Location])

You can literally copy and paste what is below

**Description**
For clarity, these code blocks are in markdown, although in GitHub,
you may just use their formatting tools. There should be a
basic description providing a dev-friendly summary of the issue or
feature. This part is optional but recommended.

**UC**
* As a ____, I want to ___ in order to ____

This section should contain a couple of Agile-style use cases
or user stories (1 or 2, 3 max). Each one of them should be their own bullet
point and be clear enough to understand if you looked at it again
in ten years. If you find it impossible to write even one of these,
then it is likely because this is not a ticket that addresses a
user's need.

**AC**
* Focused descriptions of acceptance criteria for this section
should be provided as needed. E.g.:
* When the "submit" button is hit on this screen, the form should
POST data to the API, and
* After the API sends a response, the user should be redirected
to another page, where they can modify their submission.