This is an old revision of the document!
When you log into your account on Converter Plus there is a link at the bottom of the page called Request Tracker
. This will take you to a page were you can report any errors, bugs, or user feedback. You can also track other reports that have been previously logged.
At the bottom of the page you will find a section for New Issue
.
To send a report:
Report a new issue
Category
= choose appropriate categoryTitle
= name the error/issue/feedback. Make it clear and concise so it is clear what the report is about.Project
= enter the file title as it appears in Converter Plus. This will help the developer find the specific file. If it is general feedback, leave blank.Location of Problem
= name of your profile, where you were when the issue occurred (e.g. Track 5) or location of function you are giving feedback for.Steps to Reproduce Problem
= exactly what you did before the error occurred. Remember to be a precise as possible so the developer can recreate the issue. If you are reporting functionality feedback you can leave blankError Message
= copy and paste the error message. It is very important to have it exactly as it appears on your screen.Additional Details
= any other notes that will help the developer. Again, be very clear and include as much information as you can. If you have any suggestions for improvements, include them here as well.Example of a good bug report:
"Hi, I encountered an error when splitting a track. The book is under the account for Elizabeth and entitled RoughingIt. I selected Track 14, pressed Edit, and pressed Scan. It showed a time index of 1215, which was perfect. When I pressed Split, the following error was displayed. … I closed the browser as soon as the error came up, and will wait for instructions."
If you think the program malfunctioned, please immediately stop using it. Do not look at the book, or hand it to someone else. Copy the full text of the error, close your browser, Email your team lead, and wait for instructions.
If you have an issue with the file, such as it is not divided into proper chapters or the file on NNELS is incomplete, you can pass the book to Rachel without exporting it. Please see Hand to Rachel for more info, and follow the same template for reporting the issue.
If you are creating a log for feedback on usability, please include as much details as possible including:
Any questions or concerns around your work beyond this you can post it on the Q&A page.
It is important you go through this documentation and process carefully. This project is all about paying attention to detail and asking questions if anything is confusing.
When you have finished a book you will export it and Send to QA to Check.