Fix reversed priority colors in project views - #46
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughA new centralized Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~13 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|



What changed
Fixes #42
This fixes the priority flag color mapping in the Projects UI so it matches the actual priority convention used in the codebase:
P1= Urgent = rose/redP2= High = orangeP3= Medium = amberP4= Low = slate/grayThe bug was caused by duplicated priority color mappings in multiple components that had the scale reversed. I moved the priority display metadata into a shared
priorityOptionssource and updated:KanbanCardCardDetailModalProjectsFilterBarPriorityPickerto use the same canonical mapping.
Why
PriorityPickeralready had the correct mapping, but the other project views were showing the opposite severity colors. This made urgent items look low priority and low-priority items look urgent.Verification
npx tsc -bSummary by CodeRabbit
Release Notes