Test Plan/Test Execution Records/Last Result
Following the above "path" and getting to the "Execution Result" users cannot Create defects in the associated RTC, but Linking with existing works ok.
1st attempt to Create defect in the session shows (briefly) a message about initializing the service, then clicking the button gain does nothing.
Opening Firebug on the page hits an exception :
on if (_4f.isArray() )
In the url stack there is a callout to the RTC server for some ajax
/jazz/_ajax_modules/com.ibm.team.workItem.WIPicker?projectAreaID=...&showLoginLink=true&...
So it appears to be trying, just doesn't complete the transaction.
Any suggestions ?
RQM 3.0.1.2, RTC 3.0.1
1st attempt to Create defect in the session shows (briefly) a message about initializing the service, then clicking the button gain does nothing.
Opening Firebug on the page hits an exception :
var _4d=(_4c&&dojo.isArray(_4b))?_4b.length-1:0;
for(var i=0;i<_4d;i++){
var _4e=_4b[i];
var _4f=_4c.getAttribute(_4e);
if(_4f.isArray()){
_4c=_4c.getAttributeArrayValue(_4e,0,true);
}else{
_4c=_4c.getAttributeValue(_4e,true);
}
on if (_4f.isArray() )
In the url stack there is a callout to the RTC server for some ajax
/jazz/_ajax_modules/com.ibm.team.workItem.WIPicker?projectAreaID=...&showLoginLink=true&...
So it appears to be trying, just doesn't complete the transaction.
Any suggestions ?
RQM 3.0.1.2, RTC 3.0.1
One answer
Can you run application in debug mode to get detail log in fire bug
To run RQM web client in debug mode
Try this https://<server>:port/qm/web/console/<project>?debug=true
Essentially add ?debug=true to the url. Update with the exception log.
Between also clean browser cache in case server was recently upgraded.
To run RQM web client in debug mode
Try this https://<server>:port/qm/web/console/<project>?debug=true
Essentially add ?debug=true to the url. Update with the exception log.
Between also clean browser cache in case server was recently upgraded.