I think you'd be far safer either
1. Reopening the issue, fixing and closing
2. Creating a temp workflow transition to reopen it to resolved, fix and close
Not sure if you already do this, but I recommend NOT closing issues until the version is done and dusted (possibly even archived etc..) Then bulk close, that way you get a chance to do some cleanup like you are doing
A similar question here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Renjith. I have the default workflow - because my JIRA installation is only small (for me) I will just adjust my "Issue Closing" habits for now rather than learn more of the workflow stuff - it looks like a worthy part to explore when I have more time :)
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you'd be far safer either
1. Reopening the issue, fixing and closing
2. Creating a temp workflow transition to reopen it to resolved, fix and close
Not sure if you already do this, but I recommend NOT closing issues until the version is done and dusted (possibly even archived etc..) Then bulk close, that way you get a chance to do some cleanup like you are doing
However, if you DO want to mark it in the database the table is jiraissue and the column is fixfor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
mate that is an excellent tip looking forward - thank you very much!
and for the sql - handy for next time... i only had 45 issues to painfully reopen fixfor resolve close :) about 150 notifications in my inbox.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.