<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi, swift-dev et al (but especially Ted). I’ve recently noticed that our JIRA workflow has been a bit confusing. We currently have five “statuses":<div class=""><br class=""></div><div class="">1. Opened: This bug has been filed.</div><div class="">2. In Progress: Someone is actively working on this bug. (Not everyone has been bothering to set this, but it seems reasonable to have.)</div><div class="">3. Resolved: A fix has been merged to master.</div><div class="">4. Closed: The fix has been verified by the reporter.</div><div class="">5. Reopened: The “fix" doesn’t actually fix the reporter’s problem.</div><div class=""><br class=""></div><div class="">The problem is that the “Resolved” and “Closed” statuses aren’t really distinguished on the site itself—it’s unclear for a contributor which one they’re supposed to use when they get something merged, and it’s unclear for the reporter what <i class="">they’re</i> supposed to say. Therefore, <b class="">I suggest changing the “Resolved” status to “Verify”</b> (like we use in Radar) and the “Resolve Issue” button to “Mark Resolved”.</div><div class=""><br class=""></div><div class="">(There are other things unspecified here, such as how to track what release a fix gets into, or what the story is for the Assignee field, but we can discuss those later.)</div><div class=""><br class=""></div><div class="">What do you think?</div><div class="">Thanks,</div><div class="">Jordan</div></body></html>