In Jira Product Discovery (JPD), date fields can be configured to visually indicate when a date is overdue or at risk of becoming overdue. However, the current formatting is based solely on the calendar date itself, without considering the item's status.
This can lead to misleading results. For example, if a ticket has a Start Date in the past and is currently In Progress, JPD will still highlight the Start Date as overdue. In reality, the work has already started, which means the Start Date was met and is no longer overdue. The overdue formatting should only apply when the Start Date has passed and the work has not yet started.
Ideally, the date formatting would take the item's status into account. For example:
This would provide a more accurate representation of schedule risk and reduce false overdue indicators.
Hi @Benzi Zaslavsky, the rule reads that one date field and nothing else. Tanguy Crusson from the JPD team answered the same ask in Sep 2024, "the formatting applies (or not) purely based on this date field (not a combination of field values)", and the current doc still describes a rule as colour and emojis when the date is approaching or overdue. Nothing has moved on it.
So stop making the date field carry the meaning. Add a single select, colour its options, and set it from an automation rule that fires when the date has passed while the idea is still in a pre-work status, then colour by that field. You give up the automatic date maths and take on a rule to maintain. Test it on one idea before you roll it out.
Send it through in-product feedback as well. Per-view formatting was the version of this the team had discussed back then, and it wasn't roadmapped.
I think this would make the overdue indicators much more meaningful. Right now the formatting only answers "has this date passed?" when what most teams actually care about is "is this work late given its current state?"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.