Pain point · Reliability & bugs · Blocks work
Resolved in next release picks the wrong release, causing false regressions
1 source thread · first seen 2025-04
Summary
On an iOS project, marking an issue resolved in the next release records the wrong baseline build, so the issue is immediately marked as a regression.
- Affects
- iOS teams using release tracking
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“This then means that the next time this issue occurs in 4.6.1 (5) it is immediately marked as a regression”