This is a fun bug for first time users of Litmus... STR: 1. Create a testgroup 2. Create a couple subgroups 3. Go to manage_subgroups.cgi 4. Edit your already created testgroup 5. Try to add a subgroup and note that the list "All Subgroups For Product/Branch" is blank. The reason it's blank is because "branch(es)" is a required field. Unfortunately, you can't specify a branch for subgroups. Workaround: Deselect any branches in your testgroup. The subgroups will appear and you can add them to the test group. Then you must re-add the branch to the testgroup before you submit your edits, else it will fail.

One way to fix this issue is to allow/require admin users to add a new testcase to an existing subgroup when the testcase is initially created. This will setup that initial branch relationship that is missing now. The same applies to adding new subgroups to testgroups. However, this will really only fix the issue for new testcases. Cloned testcases will continue to have to use the workaround to change the branch/testgroup/subgroup, unless we make the cloned testcase interface more elaborate than the current single button click.

Each testgroup, subgroup and testcase should belong to a single branch. This is how we are effectively using the system now, and will eliminate the branch selection problem we are experiencing. This will require: * collapsing the testgroup_branches table into the testgroups table; * adding branch_id fields to both subgroups and testcases; * changing the management interface for each; * changing the display for each; and, * changing the search tools to allow for searching by branch Fairly invasive, but it needs to happen.

Committed, and production install updated. There is a script, migration/update_branch_relationships.pl, which admins should run. This script will do the heavy lifting in terms of mapping existing testgroup->branch relationships over to subgroups and testcases.

Works great! Thanks Chris!