Close an issue

The reporter just confirmed the bug is fixed in the sprint build. Close the issue assigned to Maya, add a short note thanking the reporter and linking the release that contains the fix, and move the issue card to Done in the sprint board.

Before closing this bug, make it easy for stakeholders to verify closure: surface the exact commit and release that fixed it at the top of the issue, note the verification steps the reporter followed, and flag if any related issues might still be open and need linking.

The reporter commented that the bug appears fixed in today’s build but did not provide repro steps or environment details. I am hesitant to close because I don’t know if it’s truly fixed across supported platforms. Should I close and reopen if it resurfaces, ask for details now, or run a quick smoke test myself? What’s the best next move given I have limited time this afternoon?

We keep accumulating issues in the backlog that get labeled and assigned but are never closed because verification stalls or releases slip. Which habit is costing us the most time or credibility, and what one change to issue triage or release notes would stop this leak and reduce rework?