This content has been marked as final.
Show 3 replies
-
1. Re: jira cleanup
kukeltje Jun 16, 2008 2:15 PM (in response to tom.baeyens)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 Jun 17, 2008 3:04 AM (in response to tom.baeyens)"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
kukeltje Jun 17, 2008 4:18 AM (in response to tom.baeyens)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)