[Building Sakai] General Jira workflow question - ready for merge, no QA

[Neal Caidin]

Hi all,

If a Jira bug is ready for merging to one or more branches and shows that in the 2.y.x status fields (e.g. 2.9.x, Status 2.8.x Status, etc) , has been identified as Fixed by the developer, is Resolved status, but really cannot be functionally tested, what is the next step in the workflow?

The options in the workflow, after Resolved, are:

* Tested
* Reopen
* Close without testing
* Start QA

The ticket should not be Close without testing, since it hasn't been merged yet. We don't want to Start QA, since we are not doing any QA. Maybe we should click Tested so that the issue will show as Verified, and be a signal that it is ready for merge to the branch managers, even though no testing was actually done? I would be inclined, at least until I get more familiar with things, to check with the Assignee (aka the developer) first, to make sure I'm making a correct assumption. Just trying to get my brain wrapped around the workflow.

Thanks,

Neal Caidin

Sakai CLE Community Coordinator
nealcaidin at sakaifoundation.org
Skype: nealkdin
AIM: ncaidin at aol.com