Content Rules
Closed this issue · 0 comments
Graeimh commented
Context
No assigning unless absolutely necessary (it’s all pull)
TITLE
Type of changes:
- feat - for feature
- fix - for hotfixes/bug fixes
- chore - for debt recovery
changes / specifics: description
LABEL
🐛Bug
🥚Breaking change
💽Database
♻️Depedencies
📚Documentation
🎨Design
💡Feature
🥬Java/Spring
🟨Javascript
🆘Help Wanted
🛡️Security
PRIORITY
🚩Flagged: Urgent because it either affects the current release or blocks/affects important tickets
⏫Very High
🔼High
⏹️Medium
🔽Low
⏬Very low
Contents
🗒️NOTES
Anything relevant to the issue's state or any additional description.
🏁MILESTONES
- DOR
- DOD
📜CONTEXT (User Story)
As a dev/admin/user
I want to develop/manage/use
In order to work
🪜STEPS TO FOLLOW
- Step 1: Step 1
- Step 2: Step 2
- Step 3: Step 3
🪳STEPS TO REPRODUCE (If it is a bug)
- Step 1: Step 1
- Step 2: Step 2
- Step 3: Step 3
✅ACCEPTANCE CRITERIA
- ⛔Acceptance criterion not-met
- ✅Acceptance criterion met
📛BLOCKERS
- 📛Blocker still present
Blocker dealt with
🔍AFFECTED COMPONENT(S) (Scope)
/src/…
⛓️LINK TO OTHER ISSUES
🪟SCREEN SHOTS & MOCKUPS
Here you can insert screen shots, pictures or figma links pointing to a visual representation of what is expected
📋TEST STATUSES
What kind of tests has been put in place to ensure the issue is resolved?
- Manual Tests
- Unit Tests
- Integration Tests
- Functional Tests
- End To End Tests
- Other