GitHub Projects Board Setup Guide — Laundry Management System¶
Document Information¶
| Field | Value |
|---|---|
| Project | Laundry Management System |
| Version | 1.0 |
| Document Type | Setup Guide |
Step-by-Step Setup¶
Step 1: Create the Project Board¶
- Go to
https://github.com/unitydevs-ly/Laundry-system. - Click the Projects tab at the top.
- Click New project (green button, top right).
- Choose Board layout (Kanban).
- Name it: Laundry System
- Click Create project.
Step 2: Configure Columns¶
Delete the default columns and create these:
| Column | Purpose |
|---|---|
| Backlog | Approved features/bugs, not yet scheduled |
| Sprint Backlog | Items selected for the current sprint |
| In Progress | Currently being worked on |
| Review | PR opened, awaiting code review |
| Done | Merged to develop and deployed (staging or production) |
To add columns: Click + next to the rightmost column header.
Step 3: Add Custom Fields¶
Click the ... menu (top right) → Settings → Custom fields.
| Field | Type | Values |
|---|---|---|
| Priority | Single select | P0 - Critical, P1 - High, P2 - Medium, P3 - Low |
| Type | Single select | Feature, Bug, Chore, Docs, Spike |
| Sprint | Single select | Sprint 1, Sprint 2, ... (add as sprints are planned) |
| Phase | Single select | Phase 0: Setup, Phase 1: Master Data, Phase 2: Invoices, Phase 3: Accounting, Phase 4: Carpet, Phase 5: Tailoring, Phase 6: Inventory, Phase 7: Sync, Phase 8: Returns, Phase 9: Reports, Phase 10: Polish |
Step 4: Link the Project to the Repository¶
- In the project board, click ... → Settings.
- Under Linked repositories, search for
unitydevs-ly/Laundry-system. - Click Link.
Now any issue created in the repo can be added to this project.
Step 5: Configure Workflows (Automation)¶
- In the project board, click ... → Workflows.
- Enable the following built-in workflows:
| Workflow | What It Does |
|---|---|
| Item added to project | Set Status to "Backlog" |
| Item reopened | Set Status to "In Progress" |
| Pull request opened | Set Status to "Review" |
| Pull request merged | Set Status to "Done" |
| Item closed | Set Status to "Done" |
- Click each workflow and configure the target status.
Step 6: Seed the Initial Backlog¶
Create issues for the Phase 0 tasks. Example issues:
| Title | Type | Priority | Phase |
|---|---|---|---|
| Repository setup with Git Flow branches | Chore | P0 | Phase 0 |
| GitHub Actions CI/CD pipelines | Chore | P0 | Phase 0 |
| Docker Compose configuration (dev + prod) | Chore | P0 | Phase 0 |
| ASP.NET Core solution structure (4 projects) | Chore | P0 | Phase 0 |
| Angular project scaffolding | Chore | P0 | Phase 0 |
| Tauri initialization + plugins | Chore | P0 | Phase 0 |
| EF Core Code-First + initial migration | Chore | P0 | Phase 0 |
| TestContainers + Jest setup | Chore | P0 | Phase 0 |
| ESLint + Prettier configuration | Chore | P0 | Phase 0 |
| Serilog + OpenTelemetry + Seq configuration | Chore | P0 | Phase 0 |
Repeat for each phase when the sprint for that phase is planned. Use the docs/Project_Execution_Plan_EN.md task list as the source for breaking down epics into issues.
Step 7: Daily Usage¶
- Sprint Planning: Move items from "Backlog" to "Sprint Backlog". Assign to team members.
- During Sprint: Team members move items to "In Progress" when starting work.
- PR Opened: GitHub automation moves the item to "Review".
- PR Merged: GitHub automation moves the item to "Done".
- Retrospective: Review what was completed vs planned. Move unfinished items back to "Backlog" or to the next sprint.
Using the Project Board with Issues¶
Creating an Issue for the Board¶
- Go to Issues tab in the repo.
- Click New issue.
- Fill in the title and description.
- In the right sidebar, under Projects, select Laundry System.
- Set the custom fields (Priority, Type, Sprint, Phase).
- Click Submit new issue.
Converting a PR to an Issue on the Board¶
When you open a PR, if it should move a board item:
1. In the PR description, write Closes #<issue-number>.
2. When the PR is merged, the issue auto-closes and the board item moves to "Done".
GitHub Projects vs External Tools¶
You chose GitHub Projects over Jira/Trello because: - No extra cost (free with GitHub). - Tight integration with Issues, PRs, and CI/CD. - Single source of truth alongside the code. - No separate login or tool to manage.
Revision History¶
| Date | Version | Author | Changes |
|---|---|---|---|
| 2026-05-10 | 1.0 | DevOps Lead | Initial project board setup guide |