This guide aims to help you overcome some frequent mistakes. It consists of cases we’ve gotten so far and solutions to these common problems. If none of these solutions work for you, submit a ticket to us or mail us at email@example.com. We’re here to help.
Here are some typical issues encountered while submitting bugs to your preferred tracker:
We should note that there are two different types of Web URL, one for GUI (Graphic User Interface) and one for Web Service. In many cases their appearances look alike. Take this case as an example:
The url for web service schema depends on the way your IT administrator is setup. The common schema is http://yourserver:portnumber . Contact them to get the correct url for web services.
Look into the following case:
When submitting a defect to VersionOne through qTest eXplorer, the Summary/Trace Steps are not placed in the correct field in the VersionOne defect. The steps are placed in the “Description” section rather than the “Steps to Reproduce” section.
VersionOne does not allow qTest eXplorer or other applications that want to integrate with Version to query its custom fields either. So qTest eXplorer has no knowledge about whether there is a custom field named Steps to Reproduce on VersionOne or not (some admin will add this field and possibly name it a bit different than "Steps to Reproduce", and some will just use default VersionOne configuration that does not have this field).
At this point, users may have to manually update the ticket on VersionOne after submitting it to Version. In future releases, we are considering allowing users to map fields on qTest eXplorer with fields on VersionOne, save and share these mapping settings with other people in team.
** Learn more about submitting defects to other trackers at Submit Defect to Defect Tracking Systems.