This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
🛠 Standard Practice with Issues
Keep issue statuses accurate and up to date. If needed, add detailed descriptions outlining the scope and required steps.
Assignees should regularly update their issues to reflect current progress.
Example update: Issue #66
Important
Issues aren't just for team transparency — they're for you, too. Keeping track of your progress helps you quickly get back on track if interrupted, and enables others to take over if needed.
⏱ Estimates
Estimates are intentionally rough. Spend no more than 1–2 seconds deciding.
Use the Fibonacci scale (1, 2, 3, 5... up to 32):
- 1 = 15 mins to ~2 hours
- 2 = ~1 to 4 hours
- 32 = 1–7+ days
Update estimates if the actual time taken differs significantly.
Note
Estimates weren’t used in Phase One — we’ll adopt them consistently in Phase Two.
🧩 Epics
Epics group related tasks under a larger feature or goal. When all child issues are done and the main objective is achieved, the epic can be closed.
More on epics: Atlassian Docs
📋 Planning Board & Issue Statuses
The Planning Board is our main workspace for tracking overall project progress.
No Status
Placeholder issues — not yet evaluated or prioritized.
Backlog
Tasks planned for future work.
In Progress
Active tasks. These should be specific and reflect current work.
Each team member should only have one issue in progress at a time.
In Review
- Awaiting team review (all assigned)
- Awaiting review by another team member, Claymore Thistle, or Tutor
Blocked
Tasks we can’t proceed on yet — due to:
- Pending input from Claymore Thistle
- Dependencies on other team members or tasks
E.g., a login system blocked by a missing database schema.
Done
Completed work. Can be reviewed or reopened later if needed.