[dklawren]

Changes (2 files, not committed):

1. Bugzilla/API/V1/Util.pm:361: when type('dateTime', …) gets a value that datetime_from() can't parse, it now returns the raw string instead of crashing on undef. Valid dates still come back as ISO 8601 with a Z.
2. t/api-util-type-datetime.t (new): checks a valid date, an empty date, undef, and the joined value from bug 2048343. 4 of 4 pass.

[Copilot]

🟢 Approval recommended

No active review issues were identified for the change intended to prevent REST bug-history failures on unparseable date values.

No open issues 🎉

What changed in this PR

Prevents REST bug-history requests from failing when a date value cannot be parsed, such as joined activity values.

Changes:

• Returns unparseable date values as raw strings instead of calling iso8601() on an undefined value.
• Preserves UTC ISO 8601 formatting for valid dates and empty-string handling for missing values.

File	Description
Bugzilla/​API/​V1/​Util.pm	Adds a safe fallback for unparseable dateTime values.

_{Review effort: Balanced}

[Xzzz]

LGTM, Thanks!
Just one thing: the description mentions a new t/api-util-type-datetime.t, but it isn't in this PR. Is it wanted?

[cgsheeh]

The PR description mentions a new t/api-util-type-datetime.t test, but it isn't in the diff. Was it left uncommitted? It would be good to include it, ideally with the joined value from bug 2048343.