Hi All, To make the project better organized, I want to resurrect the discussion on - http://markmail.org/thread/c6bmzb7pb5t3ywl3 and in addition I propose the following guidelines in effectively utilizing JIRA. We can iterate, agree and document on the website.
1) Assign appropriate JIRA type to all the new issues. Pick among: Bug, New Feature, Improvement, Wish, Task, BrainStorming. 2) As much as possible, lets attach the JIRA tasks to a target release. This will help in quickly prioritize blockers for next immediate release. Secondly, it will make the release management easy by quickly browsing through a tagged JIRA release and get the full change log. We do not want to slow down adding JIRA tasks, so at the If a task/sub-task is not decided or cannot be determined then assign it to a release called WISHLIST (a version i added to JIRA). 3) Resolve Vs Close: Once the developer fixes the issues and commits the change, he/she will resolve the issuer. The reporter verifies the issues and if fixed/addressed closes the issue. In cases where users do not close the tickets, based on confirmation (within mailing list of by comments) that the issue is fixed, the dev may close the ticket. In the most common cases where a developer opens a ticket and works on a problem and resolves it, if they believe that the issue is addressed to their satisfaction, or no further work is needed, then they can directly CLOSE the issue bypassing the RESOLVE. As much as possible, we have to encourage developers to resolve the issues and reporters to close the tickets. In the case, when none of the above criteria apples or lack of response, any developer may choose to go through the tickets, understand the report, verify the resolution and if addressed, close the issue. Alongside this discussion, please spare some time to go through current RESOLVED JIRA tickets http://goo.gl/cUOPo and verify if the issues and close them appropriately. Cheers, Suresh
