IssueFlow is a modern issue tracker for engineering teams. It lets you create, organize, search, sort, and filter issues — and share a filtered view of your board with anyone via the URL.

The project is a hands-on, end-to-end build covering a production-style Next.js App Router application backed by Supabase (Postgres), including database design, migrations, seed data, server-side data fetching, and a polished UI.

• 🗂️ Issue list with rich cards showing status, priority, labels, and assignee
• 🔍 Search across issue titles and descriptions
• ↕️ Sorting by created date, priority, or title (ascending/descending)
• 🎛️ Filtering by status, priority, and assignee — all combinable
• 🔗 Shareable filters — active filters are reflected in the URL so you can copy and share a filtered view
• 📄 Pagination with configurable page size
• 📊 Dashboard with issue statistics (To do / In progress / Done)
• ⚡ Loading, empty, and error states throughout

Follow along with the full build on YouTube:

👉 Build IssueFlow — watch the video

• Node.js 20+ (the project is developed on Node 22)
• npm (or your preferred package manager)
• A Supabase project — cloud or local (see Supabase setup)

git clone https://github.com/tapascript/issueflow.git
cd issueflow

npm install

Create a .env.local file in the project root and add your Supabase credentials:

NEXT_PUBLIC_SUPABASE_URL=your_supabase_project_url
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=your_supabase_publishable_key

You can find these in your Supabase dashboard under Project Settings → API (see Supabase setup below).

npm run dev

Open http://localhost:3000 to see the app.

IssueFlow uses Supabase (Postgres) for storage. All schema definitions live in the supabase/ directory as SQL migrations.

1. Create a project at supabase.com.
2. From your project dashboard, open Project Settings → API and copy:
   • The Project URL → NEXT_PUBLIC_SUPABASE_URL
   • The publishable key (or anon key) → NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY
3. Run the migrations and seed data against your project:

npm install -g supabase
supabase link --project-ref <your-project-ref>
supabase db push

supabase db push applies the migrations in supabase/migrations/ (including the seed data) to your remote database.

If you prefer to develop against a local database:

supabase start
supabase db reset

• supabase start boots a local Postgres + API (default API URL: http://127.0.0.1:54321).
• supabase db reset applies migrations and seeds fresh local data.

Then point your .env.local at the local instance:

NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=<local-anon-key-from-supabase-status>

The database consists of four tables:

Primary key is the composite (issue_id, label_id).

The schema also includes:

• Indexes on status, priority, assignee_id, and created_at for fast filtering/sorting.
• A set_updated_at() trigger that keeps issues.updated_at in sync.
• Row Level Security (RLS) policies for profiles, issues, labels, and issue_labels.

If you find IssueFlow helpful, please consider supporting the work:

• ⭐ Star this repository — it really helps!
• 🎥 Watch the build video → youtu.be/Ms9VOyoWDpI
• 📺 Follow the tapaScript channel for tech career growth, tutorials, and more → youtube.com/tapasadhikary

MIT © tapaScript