JIRA Workflow Model Update

[Dave Ings <ings@ca.ibm.com>]

Hi,

At the 8/6 TC we formally agreed that the revised JIRA workflow model would be: "New", "Open", In Progress", and then finally "Resolved". The scenario we were trying to address was that JIRA made it hard to browse open but unassigned (i.e. not being actively worked) issues.

I've been in touch with Mike Edwards (who manages JIRA for us) and there is a glitch. He can't make this change without consulting with all the SCA TCs, because we share a server instance with them and you can't have multiple workflow models per instance.

Mike and I looked further at this. He made a config change to JIRA, so that you can now open a new issue with the assignee "Unassigned" and then you can filter on all new or open "Unassigned" issues. We've tested this and it seems to work fine.

Does this satisfy our requirement? I think it does, and if the TC agrees at the next TC I'd like to vote on reverting to our previous process model but with the use of "Unassigned" as suggested above.

Regards, Dave Ings,
Emerging Software Standards
Email: ings@ca.ibm.com
Yahoo Messenger: dave_ings