Now available in the open beta for ClearQuest 8.0.1 is the improved ability to update multiple records in the ClearQuest Web client. ClearQuest development has recorded a demonstration of the changes and would like your feedback!
In ClearQuest Web 7.1 and 8.0, it was only possible to perform simple modifications to multiple records. The feature now has several improvements, including the ability to perform state transitions on multiple records. You can find the demonstration of these changes in the download list for the ClearQuest Open Beta.
This feature is still in development, and your feedback is appreciated to help with improvements. See ClearQuest Open Beta Support for info on posting feedback or questions. Keep in mind that ClearQuest 8.0.1 is in beta and is subject to change. See the open beta website for more information on the program's terms and conditions.
dmmckinn 1200006SCS Visits (356)
If you are planning an installation or upgrade of ClearCase or ClearQuest in the near future, the following information will be helpful. Certain integration solutions and operating systems will no longer be supported in 2016.
Refer to the following recently published planning document for further details:
Additional information about end of support for individual products versions is also available on the IBM Software support lifecycle pages at the following links:
dmmckinn 1200006SCS Visits (378)
Our peeps have been busy creating videos to help you get the most out of our products. Check out these recently published educational videos.
GlennSkinner 110000DAAT Visits (539)
Everyone has them, you know, those ages old ClearQuest records with a never ending string of history records. Records so long that you go for coffee while the record is loading. We all know them far to well. They are the bane of ClearQuest admins world wide. Well not any more. Beginning with the release of feature level 9, now we have choices.
We now can:
* Turn off history all together.
* We can turn it off for some actions and not others
* We can defer loading the history until we need it.
All of these new features opens a whole new world of management options. My favorite is simply defer loading the history. If we are making an update to a record, most of the time we don't need to see the history, so why wait for it to load. With this feature there will be a load history button on the history tab. if you need to see the history, simply click on the button. Any modification to the record, or refresh will cause the history to be discarded from memory and you will again be presented with the button.
Simple clean and neat.
For more information on these new features see the following links:
GlennSkinner 110000DAAT Visits (611)
You just upgraded WAS 8.5.x to the latest fixpack and after restarting the services, ClearQuest can no longer be accessed through port 80. You discover that you can reach it on port 12080. On closer examination, you realize the plugin-cfg.xml that is referenced by the httpd.conf file has been overwritten. How do you fix it? If you follow these simple steps below, you should be back to normal before you know it.
It turns out the httpd.conf file is not pointing to the plugin-cfg.xml being used by WAS. The file specified in httpd.conf has incorrect server paths. Propagation will fix this mismatch.
To fix this:
1) login to the WAS admin console http
2) On the left of the console expand Server -> Server Type -> Web Server
3) When the propagation is finished, Click on "<yo
4) navigate down the page and click on "Copy to web server key store directory"
Should you still have issues after performing the above, check the plugin log file for any errors.