Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
When Clara's reply to a resident, prospect or vendor is waiting for a teammate to approve it, she cannot see that reply in her own history. So on her next turn she either says the whole thing again or acts as though she never answered. This change lets her see it, marked as written but not sent yet. Nothing about what anyone receives changes, and nothing sends any earlier. It is finished, reviewed clean, and has been held for Fede for five days. Does Fede want it to go out?
2 other sessions waiting on this same answer.
WHAT WAS FOUND AND FIXED WHILE BUILDING THIS, because it belongs in the same breath. Because Clara can now see her held reply, she correctly stops repeating it. But on email, the older waiting reply was then thrown away with a note nobody was pointed at. A prospect told 'Saturday at 11 works, you are booked' who then asked about pets would never have heard the tour time. The reviewer caught it, not this session. It is fixed, it has a test that fails without the fix, and it went live in production today. ONE KNOWN GAP, LOGGED WITH AN OWNER, NOT FIXED HERE: if a teammate rejects a waiting reply, it goes back to reading as though it was sent. Same family as the bug above. It needs a change on a path this work does not own, so it is tracked separately rather than bundled in late. WHAT THE EVIDENCE DOES AND DOES NOT SHOW: the test case for the newest situation scores the same with and without the fix, so it guards against the problem coming back rather than proving the fix works. What shows it works is that the text Clara is given differs in both places it is built, on exactly the affected case, and is identical on all eight others, plus a guard that goes red if the fix is deleted. The overall score moved within noise on identical text, so it should not be read as a change. STILL OWED AFTER RELEASE: one real end-to-end on a live send path, which for email runs after deploy rather than before. THE COST OF THE WAIT, and this is not an argument to say yes: five days held, and the main branch moved underneath it twice, each time needing a repair and a fresh review round on a reviewer pool that is a single account.
0368f497 is parked on this. 2 other sessions waiting on this same answer.
190dd264 frozen pane asked it this way:
Do you want to proceed?
57769700 frozen pane asked it this way:
Do you want to proceed?