templates for writing tickets #issue-ticket

bug.md

Currently:

[What happens now in the regression]

---

Expected:

[What the correct behavior should be]

---

STEPS TO REPRODUCE:

[If needed, add steps to reproduce]

---

REFERENCE:

[Link or attach screenshot(s) to story if relevant]

chore.md

Description:

Why is it needed? Does it help the team go faster or is it a dependency that could cause problems in the codebase if it’s not done?

---

Resources:

Including instructions, additional context, or other assets that help execute the chore.

feature.md

Business/User Value:

Description of the core problem this will solve for the user When [name situation], I want to [list motivations and forces], so I can [expected outcome]

---

Acceptance Criteria

GIVEN [necessary context and preconditions for story]

WHEN [action]

THEN [reaction]

---

Dev Notes

Relevant technical notes that developers may ask you to add to the story during weekly prep meeting (pre-IPM or IPM); sometimes they may add these themselves or add them as tasks

---

Design Notes

prototype / design link inserted here; linking to a folder of a feature is good so designers can continue updating designs without anyone having to re-update the links to each design in the stories

---

---other items that you may add to a story---

Needs PM

[Add reason for adding a label needs PM so you can view the story and remember context to unblock the story; usually this is some kind of thing we need to follow up with our client counterpart on]

---

Needs Designs

[Add reason for adding a label needs design so your designers can view the story and get context to unblock the story]