Skip to content

Prod - July 2026 release 2#2040

Merged
jmgasper merged 45 commits into
masterfrom
dev
Jul 15, 2026
Merged

Prod - July 2026 release 2#2040
jmgasper merged 45 commits into
masterfrom
dev

Conversation

vas3a and others added 30 commits July 7, 2026 10:21
What was broken
The Flexi Talent engagement summary note still said total included On Hold engagements, which no longer matches the required Active and Closed-only bucket behavior.

Root cause
The note was static UI copy and still reflected the previous bucket semantics.

What was changed
Updated the Engagement Buckets note to state that Total includes only Active and Closed engagements while preserving the Active default bucket guidance.

Any added/updated tests
No UI tests were added for this copy-only change. A related-test lookup for the touched Flexi Talent view found no matching tests.
What was broken
Completed, offer rejected, and terminated assignment rows in the Flexi-Talent engagement detail panel still showed Time Left and overdue metadata even though those assignments were no longer active.

Root cause
The engagement detail assignment renderer always displayed the time-left field whenever backend timing data existed and did not check the assignment status before treating the row as current work.

What was changed
Added a current-assignment status check for selected and assigned rows, and render the Time Left metadata only for those active statuses.

Any added/updated tests
Added an EngagementsView test covering completed, offer rejected, and terminated rows with overdue timing data to ensure their Time Left/overdue metadata is hidden.
PM-5584: Hide time left for inactive assignments
PM-5585: Update Flexi Talent bucket note
…omer-portal

PM-5255 showcase customer portal
What was broken
Active challenge schedule rows could keep a stale default/template phase end date as the calendar minimum. When a shorter persisted schedule hydrated afterward, the end-date picker could disable the next one or two days after the visible phase end.

Root cause
The schedule editor stored the first scheduled end date seen for a phase key and reused it as the active non-Design shortening guard, even when the form later received an earlier persisted end date for the same phase.

What was changed
The active phase minimum now uses the earlier of the stored baseline and the currently displayed scheduled end date, and the stored baseline is corrected when a shorter schedule hydrates. This preserves the existing no-shortening guard while allowing valid extensions from the visible end date.

Any added/updated tests
Added a ChallengeScheduleSection regression test covering hydration from a longer default schedule to a shorter active schedule, including a follow-up extension that keeps the true persisted end date as the minimum.
…omer-portal

PM-5255 showcase customer portal
…omer-portal

PM-5255 showcase customer portal
…omer-portal

PM-5255 showcase customer portal
@jmgasper jmgasper requested a review from kkartunov as a code owner July 15, 2026 00:50
@jmgasper jmgasper merged commit 125433c into master Jul 15, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants