4e5ad011ee
The urgent flag was a red emoji shown red before being set — wrong. Now reuses the exact Communications component: priorityMeta() + a priority list (Urgent/Haute/Normale/Basse/Aucune) — grey outlined_flag by default, colored only when set. - SPA: per-job flag = q-btn(icon=priorityMeta(...).icon) + q-menu list, same as ConversationPanel. setEntryPriority(name,lvl) (renamed to avoid clashing with the existing pool setJobPriority(j,p)). medium (ERPNext default) shows as grey/none. - hub: job-flags store now holds a dispatch PRIORITY (urgent|high|normal| low) overriding j.priority in buildUnassigned — needed because the ERPNext job-priority field is whitelisted to low/medium/high (can't do urgent), just like conversations keep their own priority. Lesson applied: grep for an existing symbol before declaring (2nd collision this session — techsForJob, setJobPriority). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| data | ||
| docs | ||
| lib | ||
| preview | ||
| public | ||
| scripts | ||
| templates | ||
| test | ||
| .env.example | ||
| docker-compose.yml | ||
| package-lock.json | ||
| package.json | ||
| server.js | ||