Help! Copy Tester Assignments issue

[jptest]

This may be an operator error hence posting here and not on Mantis.

I had 2 builds already. Created a 3rd one and believe forgot to copy tester assignments. So I modified the build and checked the box. To my amazement the TC count came to be higher than the # in the test plan. how can this be? Maybe I had checked the assignment box the first time I created the build and modifying it caused the issue.

When i need to create a 4th build, I copied assignments from Bld 3 and got the same high # of TCs. Deleted the bld and created 4th one to copy assignments from bld 2. This time the total TC count was lower but user filter on TCs did not bring up all the TCs (like it was missing assignments although the TCs were assigned).

I looked at "Test Case Assignment Overview" and it shows some test cases appear 2,3 or 4 times per user. some users have no replication.

Anyone have any idea what's going on? What caused the replication and how I can fix the problem?

When I get to bld 5, what can I do to get back to "normal"?

[jptest]

didn't get any explanations or assistance with this so I took the assignments from the known good build (3 builds old).

Hoped that other TCs would show as unassigned to make it easier for me to identify which ones I need to assign again in the new build but unfortunately all test cases come up assigned (as they are assigned in one build or another!) So had to look at each test suite under new build to see which one was unassigned and then to go ahead and assign them.
Now the TCs match the count in test plan. Phew!!!

Sure hope it does not get messed up again.

[fman]

There is something I'm not able to understand:
1. do anyone have signed a Service Level Agreement ? => forum users or testLink developers have to give an answer in less that 3 working days ?
2. dynamics is different IMHO:
you post on forum -> wait -> get no answer => if you think this is an issue then you go and open issue on mantis.
3. and again you have to wait till we have time to read, consider importance (from our point of view) and find resource to assign to work on ticket.

[jptest]

Sorry if I offended you or anyone else. I did not mean it in a way that you interpreted it.

All I meant was since I did not see anything, this is how I worked around it for now (meaning that it was not an expert's advise or solution).
And I wrote my workaround in the event some curious reader wonders what was done to address the issue.

If it's preferred that one should not come back to explain how they worked around their issue then I shall follow the preference.
I am new and hence not in sync with the rules or procedures of the forum.

I have taken bug like issues to Mantis and am eternally grateful to all the folks who put in their own time and skill to support the community.
This one I did not report there as it seemed like a newbie user error and did not want to waste their limited time on something other users might have been able to help with.

[jroedde]

Does anyone have idea what causes this? I am stumped on how to remove the duplicate assigned records as it puts all the metrics out of whack.

[RvdP2012]

Could it have something to do with orphaned records? Previously, we migrated from a MySql to a PostGres database for TestLink and the person doing the database migration told me that he found some orphaned records related to test plans / builds that no longer existed. After the migration we found that another one of the test plans had test cases that were assigned twice to the same person. This we couldn't clear and it was only for that test plan. All others did not have that problem. Also, since we migrated to PostGres we sometimes see a database error occur when trying to delete test cases from a test plan. The error seems to indicate that orphaned records will remain behind, but the test cases are removed from the test plan.

Could it be you have an identical problem? Check with test case execution and test cases assigned to a user.