Giving perspective to your issue reports

As experienced developers we know how painful can be dealing with issues reported without sufficient details. On the other side, we understand how time consuming it is to post detailed issue report – even experienced testers may not be sure which information in given circumstances could be useful to developers in reproducing and resolving the issue.

If you ask us, an ideal issue report (if there’s such thing) should have:

• User comment (obviously),
• Data entered by user,
• Screen capture,
• Application log,
• List of user actions preceding the problem.

How often do you have a chance to see something like that? Well… probably not often (if ever).

We’re pleased to say we’re preparing a release of a tool set that will allow users to create issues as above and spend less time doing it! Stay tuned…

Issue in JIRA submitted via LogDigger Server

Footer left

…