Summary

qTrace 2.5.1 comes with several enhancements and fixes as stated below:

• Improved installation speed for Windows 7
• Usability enhancements to the qTrace activation process
• Collection of anonymous usage statistics – See updated qTrace EULA
• Address issue where qTrace cannot submit to JIRA when bug's issue type is customized to something other than "bug"

Known Limitations 

 Integrations

• Rally: Rally gets all users from Rally for Owner field. When submitting a defect to Rally if user selects the owner who doesn’t have permission on the selected project, qTrace still submits defect successfully but the selected owner cannot view the defect on Rally.
• Assembla: Sometimes, qTrace cannot submit defect to Assembla if user changes space. In this case, system shows error message: Could not connect to the remote server.
• FogBugz:
• qTrace cannot get custom fields from FogBugz
• qTrace cannot set value for field “Notify More Users”. Hence, this field is excluded out of FogBugz defect submission.
• HP Quality Center (HPQC):
• qTrace cannot submit defect with dependent field which is checked verify value.
• Parent field is not stayed on top of child field with dependent fields.
• qTrace only supports custom field dependency between dropdown – dropdown list.
• If setting dependency on qTrace is different from setting in HPQC, qTrace allows submitting defect to HPQC. In this case, if user views the defect on HPQC, value in dependent fields are not suitable with the settings in HPQC.
• Bugzilla: Bugzilla does not support special characters
• VersionOne: qTrace does not support dependent fields

• qTest: qTrace displays unclear message when submitting defect with long titles to qTest (more than 200 characters).

• TFS2010:

• qTrace displays “field name” instead of “display name” of the fields

• qTrace cannot get “TreePath” control type. Currently, qTrace displays textbox for the fields with TreePath control type.

• JIRA:

• qTrace cannot add custom field if JIRA’s version is earlier than v4.4.x

• Fields settings are lost after upgrading qTrace from v2.5.0 or earlier versions to v2.5.1

UI Capture limitations

• Un-recognized UI controls will generate with generic descriptions such as ‘Click here’ or ‘Type here’.
• WPF: Date Picker control  – qTrace can capture step but it cannot capture image of DatePicker control on WinXP.
• WPF: List View control – qTrace cannot recognize value in list item
• WPF: Rich Text box control – qTrace cannot capture content in RichText box
• MFC: Tab control – qTrace captures tab control as “Click here”
• WinForm: Picture box control –  qTrace captures picture box control as “Click here”
• SWT: ExpandBar control – qTrace captures expandbar control as “Click here”
• SWT: Slider control – qTrace captures slider as “Click here”
• Cannot capture list/list item on Chrome. Currently, qTrace captures as "Click here"
• Cannot capture combox item value on Chrome. Currently, qTrace captures as "Select combo item"
• Extended monitor:

• Incorrect image captured when taskbar has two rows, a part of taskbar is included in the images
• Wrong arrow point of Capture modes list if DPI of monitor is different than native DPI
• Capture console – qTrace cannot capture context menu & dialog on XP and Vista.
• qTrace captures entire text on notepad or text area
• qTrace displays captured value in Chinese character when recording notepad ++
• qTrace does not capture javascript well in Firefox

Others

• Cannot define hotkey with the following combinations:
• Only number (e.g.1, 2,..) or only letter (e.g. a, b,…)
• Alt + <key> (e.g. Alt + R)
• Alt + Shift + <key> (e.g. Alt + Shift + C)