The arrow that moved both dates
Two findings: the forward arrow changed both pickers, and the P&L jumped to a random date. One control, drawn to look like part of the boxes beside it.
Two rows on a tester’s sheet, filed against different reports. On one: pressing forward in either date picker changes both dates. On the other: the Flash P&L jumps to a random date when you use the arrows. Different screens, different wording, and the natural reading is two bugs in two places.
It was one control. Every report with a date range has a bar across the top: a left arrow, a From box, a To box, a right arrow. The arrows were never part of the pickers. They moved the whole window by its own length, so a seven-day report stepped a week and a month-long one stepped a month. That is a useful thing for a bar to do, and it is exactly what the tester saw: both dates moved, and on a report they had set to an odd span, they moved to a date that looked like nowhere in particular.
A control that does not say what it does
Drawn as a bare chevron either side of a date box, the arrow reads as the date box’s own stepper, the thing that nudges one day. Everything it did was correct and everything it looked like was wrong. The fix is wording, not behaviour: the buttons read Previous 7 days and Next 7 days, with the span written into the label from the range that is set, and a hover title saying that both dates move. Nothing about what the bar does changed. Nothing about it now needs explaining.
The same family, four more rows
The same workbook had four more rows about date boxes: a statement whose To could be set before its From, a stock-movements report that accepted the same, and two required boxes with no mark saying they were required. Those are fences rather than labels, so each picker now limits the other, the required boxes carry an asterisk, and a range that runs backwards cannot be submitted from the screen at all.
When two findings on two screens describe the same control, fix the control once and the two rows close together. And when a control does the right thing and still gets filed as a bug, the bug is the label.