A common pattern I've seen at Apache is: an issue marked as Resolved when the fix is committed, then Closed when the issue is released (via a bulk change in JIRA by the release manager).
Tom On Mon, Apr 3, 2017 at 5:39 PM, Tim Armstrong <[email protected]> wrote: > I've always used "Resolve Issue". > > I think there's only a distinction for more complex workflows. According to > JIRA, "Resolving an issue indicates that the developers are satisfied the > issue is finished" and "Closing an issue indicates that there is no more > work to be done on it, and that it has been verified as complete". > > > On Mon, Apr 3, 2017 at 2:32 AM, Lars Volker <[email protected]> wrote: > >> Do we have a best practice for the Status of finished work? Currently we >> seem to use "Resolved" mostly, but sometime also "Closed". When should I >> use which one? >> >> Thanks, Lars >> >> StatusIssuesPercentage >> Open >> <https://issues.apache.org/jira/secure/IssueNavigator. >> jspa?reset=true&jqlQuery=project+%3D+IMPALA+AND+status+ >> %3D+Open+ORDER+BY+priority+DESC&mode=hide> >> 1491 >> >> 29% >> Reopened >> <https://issues.apache.org/jira/secure/IssueNavigator. >> jspa?reset=true&jqlQuery=project+%3D+IMPALA+AND+status+ >> %3D+Reopened+ORDER+BY+priority+DESC&mode=hide> >> 44 >> >> 1% >> Resolved >> <https://issues.apache.org/jira/secure/IssueNavigator. >> jspa?reset=true&jqlQuery=project+%3D+IMPALA+AND+status+ >> %3D+Resolved+ORDER+BY+priority+DESC&mode=hide> >> 3550 >> >> 69% >> Closed >> <https://issues.apache.org/jira/secure/IssueNavigator. >> jspa?reset=true&jqlQuery=project+%3D+IMPALA+AND+status+ >> %3D+Closed+ORDER+BY+priority+DESC&mode=hide> >> 45 >> >> 1% >>
