Quick Search does not find defects and enhancements
2 answers
Comments
Just check the context root after you open the project. If it's /jazz, it's in RQM.
Im in the context root /jazz while using the quick search and the work items also have /jazz context root. Here is an example link to a defect:
Im still no sure if my defects are in RQM because the namespace in the links to a test script begins with com.ibm.rqm, if i open a defect the namespace in the URL is com.ibm.team. So it could be that the work items are in RTC?
It's probably more reliable to check the shortcut of the WI (right-click on the icon and copy location), or use Firebug to check which resource URI is accessed for retrieving the WI information. If you accept that the defects are in RTC, then you should also accept that quick search in RQM will not find them.
You can follow the URL:
Comments
Donald Nong
Nov 10 '16, 4:19 a.m.Are you referring to the RQM "local" defects and enhancements? It seems that you're still using the "jazz" context root - is your environment upgraded from an even older version?
Will Girard
Nov 10 '16, 4:39 a.m.Yes we have upgraded from RQM 2 or 3 to 4, about 2 years ago. And now from 4 to 6. So we are using the old "jazz" context root.
Donald Nong
Nov 10 '16, 7:25 p.m.I have never worked on such environment before, and am not sure whether you are using RTC. If the defects are in RQM, they are sometimes referred to as "local defects", versus those in RTC as "remote defects". If during the upgrade the "local defects" somehow got migrated to RTC as "remote defects", that can explain why you can no longer "quick search" them. So you will need to determine where these defects are located now.
Will Girard
Nov 11 '16, 4:23 a.m.Thank you. Do you know how i can see if my defects got migrated to RTC?
Will Girard
Nov 11 '16, 4:23 a.m.From 5.0.2 to 6.0.2
Donald Nong
Nov 13 '16, 6:03 p.m.I would suggest you contact Support for this one so that more information can be collected to understand the issue. I've run out of ideas, sorry.