Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add board stats modal with task breakdown 📊

Open Beginner friendly
#441 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@zenithamza is already working on this.

Since Aug 28, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
javascript, react, tailwindcss
Domain
frontend

Research direction

Start in client/src/pages/Dashboard.jsx, where the issue says to add the stats button and modal. Check how the navbar and task data are currently rendered, then run the project's existing checks. Done when the modal can be opened and shows the total tasks, counts by status, and high-priority count, and closes when clicked.

Written by the indexing model from the issue text.

Description

good first issue

Add board stats modal with task breakdown 📊

File: client/src/pages/Dashboard.jsx

No way to see overall board health 💀
How many tasks per status? Per priority? fr!!

Fix: add stats button in navbar:
const [showStats, setShowStats] = useState(false)

const stats = {
total: tasks.length,
byStatus: {
backlog: tasks.filter(t => t.status === 'backlog').length,
inprogress: tasks.filter(t => t.status === 'inprogress').length,
review: tasks.filter(t => t.status === 'review').length,
done: tasks.filter(t => t.status === 'done').length,
},
byPriority: {
high: tasks.filter(t => t.priority === 'high').length,
medium: tasks.filter(t => t.priority === 'medium').length,
low: tasks.filter(t => t.priority === 'low').length,
}
}

{showStats && (

setShowStats(false)}>

📊 Board Stats

Total: {stats.total} tasks

🔵 In Progress: {stats.byStatus.inprogress}

✅ Done: {stats.byStatus.done}

🔴 High priority: {stats.byPriority.high}

)}

~25 lines! No backend needed 🎯

Dominant language
JavaScript
Stars
39
Forks
105
Avg merge
1d 12h
Merged PRs (30d)
27

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anoopcodehack/DevBoard

All issues in anoopcodehack/DevBoard

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.