tag:blogger.com,1999:blog-7285826952643196670.post7180611518632796569..comments2012-01-05T13:26:27.753-05:00Richardhttp://www.blogger.com/profile/13955040745900922376noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7285826952643196670.post-46739352277880577812011-12-20T08:57:46.000-05:002011-12-20T08:57:46.000-05:00Nice review of using the workflow!<br /><br />We had the same conversations regarding &quot;done&quot; when we moved to Jira. We decided to make a team process to handle that. If an issue is resolved, it is ready for testing, and if has been tested good it gets closed. Not very intuitive though I agree.<br /><br />We did add a step in our workflow called &quot;Waiting on Issue&quot;. It is only available if you have a link to a &quot;depends on&quot; issue or if you have a sub-task. If all the sub-tasks and linked issues that you are dependent are resolved then the issue automatically jumps from &quot;Waiting on Issue&quot; to &quot;Open&quot; and the assignee gets notified.Jameshttp://www.blogger.com/profile/02547600344144876479noreply@blogger.comtag:blogger.com,1999:blog-7285826952643196670.post-36330381143193138832011-12-20T08:55:55.058-05:002011-12-20T08:55:55.058-05:00Nice review of using the workflow!<br /><br />We had the same conversations regarding &quot;done&quot; when we moved to Jira. We decided to make a team process to handle that. If an issue is resolved, it is ready for testing, and if has been tested good it gets closed. Not very intuitive though I agree.<br /><br />We did add a step in our workflow called &quot;Waiting on Issue&quot;. It is only available if you have a link to a &quot;depends on&quot; issue or if you have a sub-task. If all the sub-tasks and linked issues that you are dependent are resolved then the issue automatically jumps from &quot;Waiting on Issue&quot; to &quot;Open&quot; and the assignee gets notified.Jameshttp://www.blogger.com/profile/02547600344144876479noreply@blogger.com