GitHub Projects is a built-in task management tool that turns your Issues into a visual Kanban board. Create a project from the Projects tab, add columns like To Do, In Progress, and Done, then drag issues between columns as work progresses. You can also switch to Table view for spreadsheet-style tracking or Roadmap view for timeline planning.
GitHub Projects Gives You a Kanban Board Built Into Your Repository
If you have used Trello, Asana, or Notion for task management, GitHub Projects works the same way — but it is directly connected to your code repository. Every Issue in your repository can become a card on a visual board. The Board view gives you a Kanban-style layout with columns like To Do, In Progress, and Done. Drag cards between columns as work progresses. The Table view looks like a spreadsheet where you can sort, filter, and group by any field. The Roadmap view shows tasks on a timeline, which is useful for planning sprints or release dates. Because GitHub Projects connects directly to Issues and Pull Requests, cards update automatically when issues are closed or PRs are merged. This means your task board stays accurate without manual updates. AI tools like Lovable and V0 push code changes that close issues, which then move automatically on your project board.
Prerequisites
- A free GitHub account
- A repository with at least a few open Issues
- A modern web browser
Step-by-step guide
Create a new GitHub Project
Create a new GitHub Project
Navigate to your repository on github.com. Click the "Projects" tab in the top menu bar. Click the green "New project" button (or "Link a project" if you already have one). GitHub shows template options — select "Board" for a Kanban-style layout. Give your project a name like "Product Roadmap" or "Sprint Board." Click "Create project." You will see a blank board with a default column and an option to add more columns.
Expected result: A new project board opens with a default column and an empty workspace ready for customization.
Add columns for your workflow stages
Add columns for your workflow stages
Your board needs columns that represent your workflow. Click the "+" button to add new columns. Create these standard columns: "Backlog" (ideas and future work), "To Do" (ready to start), "In Progress" (actively being worked on), "In Review" (waiting for approval), and "Done" (completed). You can rename the default column by clicking its title. Drag columns left or right to reorder them. Each column represents a stage in your process, and you will move cards through them as work progresses.
Expected result: Your board shows five columns: Backlog, To Do, In Progress, In Review, and Done, arranged left to right.
Add existing Issues to your project board
Add existing Issues to your project board
Click the "+" button at the bottom of any column (or the "Add item" button). In the search box that appears, type # followed by a keyword to search your repository's Issues. Select the issues you want to add — they appear as cards in the column. You can also add issues from the Issue page itself: open any issue, look at the right sidebar, click "Projects," and select your project board. The issue will appear in the default column, and you can drag it to the right one. Add all your open issues to get a complete picture of your project.
Expected result: Your project board shows issue cards distributed across columns, each displaying the issue title, number, labels, and assignee.
Drag cards between columns as work progresses
Drag cards between columns as work progresses
When someone starts working on an issue, click and hold the card and drag it from "To Do" to "In Progress." When they open a Pull Request for review, drag it to "In Review." When the PR is merged and the issue closes, you can drag it to "Done" — or configure automation to move it automatically (covered in the next step). This visual flow gives everyone on the team an instant view of the project's status. Non-technical team members can check the board at any time to see what is being worked on, what is blocked, and what is complete.
Expected result: Cards move between columns as you drag them, and the board reflects the current status of each task.
Set up automation to move cards automatically
Set up automation to move cards automatically
Click the three-dot menu at the top of a column (like "Done") and select "Set column automations" or look for the workflow settings. You can configure rules like: when an issue is closed, move it to Done; when a Pull Request is opened, move the linked issue to In Review. Click "Workflows" in the project settings (the gear icon) to see all available automations. Toggle on "Item closed" and map it to the "Done" column. These automations keep your board accurate without anyone manually moving cards.
Expected result: When an issue is closed (manually or via a merged Pull Request), its card automatically moves to the Done column.
Switch between Board, Table, and Roadmap views
Switch between Board, Table, and Roadmap views
At the top of your project, you will see tabs or a view switcher. Click the "+" icon to add a new view. Choose "Table" for a spreadsheet layout where you can add custom columns like Priority, Due Date, or Size. Choose "Roadmap" for a timeline view that shows when tasks are scheduled. Each view shows the same data in a different format. Table view is great for sorting and filtering large lists. Roadmap view is useful for planning releases and communicating timelines to stakeholders.
Expected result: You can switch between Board, Table, and Roadmap views, each showing your issues in a different layout.
Complete working example
1# GitHub Project Board Setup Guide23## Board Columns4| Column | Purpose |5|-------------|--------------------------------|6| Backlog | Ideas and future work |7| To Do | Ready to start this sprint |8| In Progress | Actively being worked on |9| In Review | PR open, waiting for approval |10| Done | Merged and shipped |1112## Custom Fields (Table View)13- Priority: Critical / High / Medium / Low14- Size: Small / Medium / Large15- Sprint: Week number or date range16- Owner: Team member responsible1718## Automations19- Issue closed → move to Done20- PR opened → move linked issue to In Review21- New issue created → add to Backlog2223## Weekly Review Checklist24- [ ] Move stale In Progress items back to To Do25- [ ] Prioritize Backlog items for next sprint26- [ ] Archive Done items older than 2 weeks27- [ ] Check for unassigned itemsCommon mistakes when using GitHub Projects for Task Management
Why it's a problem: Creating cards directly on the board instead of using Issues
How to avoid: Always create Issues first, then add them to the project. Draft cards (notes without linked issues) cannot be assigned, labeled, or linked to Pull Requests.
Why it's a problem: Forgetting to move cards when work status changes
How to avoid: Set up column automations so cards move automatically when issues are closed or PRs are opened. This reduces the manual work.
Why it's a problem: Having too many columns that slow down the workflow
How to avoid: Start with 4-5 columns maximum. Too many stages create confusion. You can always add more later if needed.
Why it's a problem: Not reviewing the board regularly
How to avoid: Do a quick weekly review: check for stale cards, reprioritize the backlog, and make sure the board reflects reality.
Why it's a problem: Using the old Projects Classic instead of the new Projects
How to avoid: GitHub has two project systems. Make sure you are using the newer "Projects" (not "Projects Classic"). The new version has Table view, Roadmap view, and custom fields.
Best practices
- Start with 4-5 columns: Backlog, To Do, In Progress, In Review, Done
- Always create Issues first and then add them to the project — avoid standalone notes
- Set up automations to move cards to Done when issues are closed
- Use the Table view for sorting and filtering large task lists
- Add custom fields like Priority and Size for better project planning
- Do a weekly board review to keep the project status accurate
- Use the Roadmap view to communicate timelines to stakeholders
- Archive completed items regularly to keep the board focused on active work
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I'm a non-technical founder setting up a GitHub Project board for my team. Help me design a column structure and workflow for managing a product built with AI tools like Lovable.
Frequently asked questions
Is GitHub Projects a replacement for Trello or Asana?
For most small to mid-size teams, yes. GitHub Projects offers Board, Table, and Roadmap views with custom fields and automations. The main advantage is that it connects directly to your code — issues close automatically when Pull Requests merge.
Can I add items from multiple repositories to one project?
Yes. Organization-level projects can pull Issues from any repository in the organization. This is useful if your product spans multiple repos.
Do AI tools like Lovable update the project board automatically?
Indirectly. When Lovable pushes code that closes an Issue (via commit messages or PR keywords), the automation moves the card to Done. You still need to manage the To Do and In Progress columns manually.
What is the difference between Projects and Projects Classic?
Projects (new) has Table view, Roadmap view, custom fields, and powerful automations. Projects Classic is the older version with basic Kanban only. GitHub is phasing out Classic — always use the new Projects.
Can non-technical team members manage the project board?
Absolutely. The board is entirely visual — drag and drop cards, add labels, assign people. No coding or technical knowledge is required.
Can RapidDev help us set up GitHub Projects for our team?
Yes. RapidDev helps teams design project board structures, configure automations, create custom fields, and establish weekly review workflows for effective task management.
Is there a limit to how many items a project can have?
GitHub Projects supports up to 1,200 items per project. For larger projects, use filters and archived items to keep the active view manageable.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation