<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=""><div class="">It hasn’t been used so much so far, but on the bugs where it has I like being able to tell the difference. I don’t think we’d poke people about verification like we do with Radar, though, so we will (and have) end up with a lot of bugs left in Resolved/Verify.</div><div class=""><br class=""></div><div class="">Jordan</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 15, 2016, at 10:10, Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com" class="">daniel_dunbar@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Do we anticipate Verify being used in practice much? <div class=""><br class=""></div><div class="">Would it be better to simplify the workflow and just have a single "Resolved/Closed/Done" state? If the originator does test the bug and find it isn't fixed, they can reopen.</div><div class=""><br class=""></div><div class="">My guess is not that many people are going to actively look at their JIRA account to find bugs that they are supposed to be verifying.<br class=""><div class=""><br class=""></div><div class=""> - Daniel</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Aug 15, 2016, at 10:08 AM, Jordan Rose via swift-build-dev <<a href="mailto:swift-build-dev@swift.org" class="">swift-build-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div 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></div>_______________________________________________<br class="">swift-build-dev mailing list<br class=""><a href="mailto:swift-build-dev@swift.org" class="">swift-build-dev@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-build-dev" class="">https://lists.swift.org/mailman/listinfo/swift-build-dev</a><br class=""></div></blockquote></div><br class=""></div></div></div></div></blockquote></div><br class=""></body></html>