3 Replies Latest reply on Jun 17, 2008 4:18 AM by Ronald van Kuijk

    jira cleanup

    Tom Baeyens Master

      we're in the process of cleaning up jira. all the issues that were not touched for at least a year have been resolved with 'out of date'.

      if you know of an issue that should not have been closed. feel free to reopen and provide a remark if you think we should reconsider.

      from now on, we're going to resolve issues instead of close.

      we have a umbrella issue that links to all candidate tasks to be taken by community members. those issues are sometimes as simple as 1, 2, 3. some are a bit more difficult. that's why the issue is numbered approprietly

      http://jira.jboss.com/jira/browse/JBPM-1234

      enjoy :-)

        • 1. Re: jira cleanup
          Ronald van Kuijk Master

          you mean as 'easy' as 1, 2, 3. Simple was with Do Re Mi


          CHORUS:
          J5: ABC
          Michael: Easy as...
          J5: 123
          Michael: Or simple as...
          J5: Do re mi
          Michael: ABC, 123, baby, you and me girl


          QED

          On a more serious note... Aren't resolving and closing two steps in the process. Often a developer resolves and issue (e.g. done) and QA closes it if it realy is done (after testing).



          • 2. Re: jira cleanup
            Tom Baeyens Master

             

            "kukeltje" wrote:
            Aren't resolving and closing two steps in the process. Often a developer resolves and issue (e.g. done) and QA closes it if it realy is done (after testing).


            yes. you are exactly right. but the problem with jira is that in order to edit closed issues, you have to reopen them. since this happens quite often, it is tedious and we just use resolved in the same way as we would use closed.

            besides, we can't really rely on the community to close issues after we resolved them.

            • 3. Re: jira cleanup
              Ronald van Kuijk Master

              It's not that the reporter should close it (not sure if he can) we can do that as well.

              Besides that, why not just close them all at once when the release goes out. If an issue is reopend afterwards, there is a reason for it (maybe we should not 'allow' reopens by procedure and just create new issues)