Canalplan Bug Tracker
Canalplan Bug Tracker
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000115||Canalplan||[All Projects] Feature Request||public||2016-05-11 07:39||2016-07-03 09:42|
|Product Version||Product Build|
|Target Version||Fixed in Version|
|Summary||0000115: Capture sessions for bug reports|
|Description||Some users are not very good at describing what they were doing when things went wrong. Others are excellent but even when they provide screen shots and details it takes a lot of work to set up the exact circumstances that caused the bug.|
Is it possible to add a hook into the report issue part of mantis that calls back to the canalplan system (even just by a "web bug" type image)? A call to the api with the issue number could capture the session and associate it with the issue number automatically, making it easy for me to rebuild the exact state CanalPlan was in when the user submitted the issue.
|Tags||No tags attached.|
|Attach Tags||(Separate by ",")|
|Is it possible to allow me to switch on a debug mode that would capture my keystrokes and screen changes so you can see exactly what is happening when a peculiar error occurs.|
|Not totally sure what you mean. Are you wanting a "Report Bug" button which when they click on it it records their session stack and then bounces into Mantis and attaches it as a file?|
|I think its best for you and Nick to decide how and who should be able to enter a "debug mode" and what info you need. Just because you can't replicate the issue on your machines doesn't mean it doesn't happen, it could be the users machine that is causing the problem (as I have experienced). This "button" should be activated by yourselves when it is deemed necessary.|
Nick Atty (administrator)
This is mainly for route-planning bugs where having all the route details and settings would help to reproduce the bug.
The idea is to have something on the page that comes up when you first report a bug (such as an image that calls back to the API) and which will trigger a copy of the session being taken and associated with that bug report.
In an ideal world it would be something on http://canalplan.eu/bugtrack/bug_report_page.php - a small image that calls - say "/cgi-bin/api.cgi?mode=bugsession&issue=bugnumber. I'm not sure, though, that the bug number is known at that time. So is it possible to hook into the call after that?
The idea is that I can have a separate interface somewhere that loads the session associated with any numbered bug and the whole thing should be transparent to the user.
Does this make sense?
|I think it does - been in SCRUM training all day so my brain is full!|
We could do this by only putting the report button there for people who are logged on.
The button could ask them to provide some more information and then it could zip up the session etc and put those files somewhere safe on the server before creating a new bug report by emailing the bugreporting address (we can set the email handler here to create new bugs).
|2016-05-11 07:39||Nick Atty||New Issue|
|2016-05-11 07:40||Nick Atty||Assigned To||=> Nick Atty|
|2016-05-11 07:40||Nick Atty||Status||new => assigned|
|2016-05-11 07:40||Nick Atty||Assigned To||Nick Atty => user3|
|2016-05-11 13:23||Shultzy||Note Added: 0000411|
||Note Added: 0000412|
|2016-05-11 13:52||Shultzy||Note Added: 0000413|
|2016-05-12 06:20||Nick Atty||Note Added: 0000414|
||Note Added: 0000417|
||Note Added: 0000578|