An issue that is well-documented is half solved. The fastest, most effective way to report an issue in a QlikView application is to take a screenshot of the anomaly using an image and video screen capture tool like TechSmith's Snagit (http://www.techsmith.com/snagit.html). Along with taking an accurate screenshot, it also allows us to easily add annotations that clearly communicate the problem.
In addition to capturing a screenshot, we can also make our troubleshooting process more efficient if we report the anomaly directly into an issue tracking system. BugHerd (https://www.bugherd.com) is a bug capturing tool that we can use to track issues or integrate it with other issue trackers, such as Jira or Zendesk. When we capture an issue in BugHerd, it takes an automatic screenshot, records information about the user's system environment, and allows the user to add any additional comment or file.
We can create a BugHerd project with the hostname, http://Qlik
ViewServerName/QvAJAXZfc and use BugHerd's Google Chrome extension in a QlikView Server environment. In case we don't use Google Chrome or we want to report issues directly in the QlikView Desktop WebView, we can use Ralf Becher's BugHerd QlikView document extension (https://github.com/ralfbecher/QlikView_Extension_BugHerd). This extension doesn't take an automatic screenshot, but we can easily attach one to the issue.
Tip
In order for the extension to work properly, you may have to add https://www.bugherd.com to the list of Trusted Sites in the Security tab found in Internet Options.
Once we report an issue, we can keep track of its status in a BugHerd project or in one of several issue-tracking tools that integrates with it. The BugHerd project uses the following Kanban board to organize issues:
Now that we've reported several issues with help from BugHerd and Snagit, let's review various issues that we commonly encounter in our QlikView applications.