Show estimated vs actual Pomodoro sessions on card ⏱️
Maintainers usually reply within 2 days
@yashTomar272 is already working on this.
Since Sep 3, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- javascript, react, tailwindcss
- Domain
- frontend
Research direction
Start in client/src/components/Board/TaskCard.jsx and inspect how the card currently displays its estimate and pomodoro count. Use the estimate-to-session mapping in the issue as the reference; done means the card shows actual versus estimated sessions when an estimate is available, with the requested color distinction.
Written by the indexing model from the issue text.
Description
Show estimated vs actual Pomodoro sessions on card ⏱️
File: client/src/components/Board/TaskCard.jsx
Estimate field exists but never compared
to actual pomodoros spent 💀 fr!!
Fix: show comparison on card:
const estimateToPomodoros = (estimate) => {
const map = {
'30m': 1, '1h': 2,
'2h': 4, '4h': 8, '1d': 16
}
return map[estimate] || null
}
const estimated = estimateToPomodoros(task.estimate)
const actual = task.pomodoroCount || 0
{estimated && (
<span className={text-[10px] ${actual > estimated ? 'text-red-400' : 'text-green-400'}}>
🍅 {actual}/{estimated} sessions
)}
~12 lines! estimate + pomodoroCount exist ✅
No backend needed 🎯
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 105
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 27
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anoopcodehack/DevBoard
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
anoopcodehack/DevBoard#589 ·
Maintainers usually reply within 2 days
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anoopcodehack/DevBoard#588 ·
Maintainers usually reply within 2 days
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
anoopcodehack/DevBoard#587 ·
Maintainers usually reply within 2 days
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
anoopcodehack/DevBoard#586 ·
Maintainers usually reply within 2 days
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anoopcodehack/DevBoard#584 ·
Maintainers usually reply within 2 days
All issues in anoopcodehack/DevBoard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 3 days
-
audit.md numbers Theming and Responsive Design differently in the headings and the score tablePossibly taken @pbakaus claimed this today. Openneeds triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
pbakaus/impeccable#979 ·
Maintainers usually reply within 1 day
-
area/web interface
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mastodon/mastodon#40924 · 1 comment ·
Maintainers usually reply within 1 day
-
fireEvent.select does not wrap its automatic native focus in actPossibly taken @sergioperezcheco claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug user-priority/P2
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day