|Anonymous | Login | Signup for a new account||2019-12-09 10:18 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002553||TestLink||Installer||public||2009-05-29 08:36||2013-05-20 19:51|
|Fixed in Version||1.9.7 (2013 Q2 - bug fixing)|
|Summary||0002553: Search function cannot search testcases created before upgrade.|
|Description||The search function does not work and shows "Your search delivered no results! " if a testcase created from the previous version of testlink(1.7.4).|
|Additional Information||The search function is working when a testcase created in 1.8.0 is being searched. |
The old issues have null as their prefix and O used this update script to try to fix the issue:
UPDATE testprojects t set prefix = "TC" WHERE prefix IS NULL;
unfortunately it still does not work.
|Tags||No tags attached.|
|QA Team - Task Workflow Status||TBD|
Are you sure that you migrate data properly?
You must do two steps:
- Upgrade DB schema
- Migrate data
I expect that you did just the first step. Could you confirm?
What I did is upgrade my current testlink then when all the issues appeared to be -0 I did this:
UPDATE tcversions a SET a.tc_external_id = (SELECT b.parent_id from nodes_hierarchy b where a.id = b.id);
Clarify: "upgrade my current testlink"
You must follow both these two links in installer:
Upgrade Database (Needed while migrating from 1.7.2)
Migration from 1.7.2 (or greater) to 1.8.0
|I did everything in the install page as instructed|
Your data migration process probably failed. I'm not able to reproduce your problem with whole description: "I did everything in the install page as instructed ".
My migration filled TC prefixes properly.
Are you able to try migration process once again and verify that no error is reported during or after process by migration script?
If you are getting the Test Case ID of "-0" then chances are you have not done the Data Migration. You most likely did just the DB schema upgrade. I just ran into the same issue of seeing the ID of "-0" for all my test cases.
Once I did the migration, the -0 was no longer there.
|2009-05-29 08:36||monsieur_jj||New Issue|
|2009-05-29 15:19||mhavlat||Note Added: 0007086|
|2009-05-29 15:19||mhavlat||Status||new => feedback|
|2009-05-29 15:19||mhavlat||Category||General => Installer|
|2009-05-29 15:22||monsieur_jj||Note Added: 0007088|
|2009-05-29 16:12||mhavlat||Note Added: 0007089|
|2009-05-29 16:19||monsieur_jj||Note Added: 0007090|
|2009-07-09 05:47||mhavlat||Note Added: 0007471|
|2009-08-27 02:42||Joe23||Note Added: 0007834|
|2013-05-20 19:51||fman||QA Team - Task Workflow Status||=> TBD|
|2013-05-20 19:51||fman||Status||feedback => closed|
|2013-05-20 19:51||fman||Assigned To||=> fman|
|2013-05-20 19:51||fman||Resolution||open => fixed|
|2013-05-20 19:51||fman||Fixed in Version||=> 1.9.7 (2013 Q2 - bug fixing)|
|Copyright © 2000 - 2019 MantisBT Team|