fix(widgets): readable dates; a used approval is not "Not approved" #21

2026-10-14T17:05:08Z

KofTwentyTwo commented

2026-10-14 17:05:08 +00:00

(Migrated from github.com)

Summary

Found in the demo screenshots:

Needs Attention ("Since") and Proposed Publication ("Scheduled for", approval time) printed raw ISO instants (2026-10-14T16:53:12.592206Z). They now read Oct 14, 2026 4:53 PM UTC.
Proposed Publication said "Not approved" while the Approvals list showed the approval as "Used by an execution". With no active approval, it now looks for a consumed approval of this exact hash and says who approved it, when, and that an execution used it (approve again to resend).

Tests

EndToEndFlowTest asserts the consumed-approval wording and the date format after the send. ./mvnw verify green locally.

🤖 Generated with Claude Code

## Summary Found in the demo screenshots: - Needs Attention ("Since") and Proposed Publication ("Scheduled for", approval time) printed raw ISO instants (`2026-10-14T16:53:12.592206Z`). They now read `Oct 14, 2026 4:53 PM UTC`. - Proposed Publication said "Not approved" while the Approvals list showed the approval as "Used by an execution". With no active approval, it now looks for a consumed approval of this exact hash and says who approved it, when, and that an execution used it (approve again to resend). ## Tests EndToEndFlowTest asserts the consumed-approval wording and the date format after the send. `./mvnw verify` green locally. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-marketing#21