Here are a few quick guidelines to follow when submitting feedback to us.
I) Logging Feedback
To the extent that the feedback can be easily recorded and sent to us please use these steps. Prompt submission is greatly appreciated.
1. How should feedback be reported?
All bugs, issues, improvement or suggestions should be emailed to email@example.com
2. What information should I include when submitting feedback?
a) Please provide an informative description regarding your feedback. Please be as specific as possible, keeping in mind that we need to convert your comment into an actionable item.
b) Provide an issue classification
Select one of the following classifications, and for improvements providing a sub-classification is very important.
I) Bug - The application isn't working correctly, and must be fixed to correct the issue.
II) Improvement - This is a suggested new feature or a way to make an existing feature more powerful or an interface more intuitive.
III.a) Improvement>Must Have - These are improvements that in your opinion must be made prior to going live with PlanGuru Analytics.
III.b) Improvement>Nice to Have - Improvements that are important, but in your opinion shouldn't prevent the application from going live.
III.b) Improvement>Great to Have - These are longer term ideas for what you might want the application to do in the future.
III) Aesthetics - These are suggestions that relate to the aesthetic representation of information within the application.
II) One-on-One follow up Sessions
As testing progresses we'd like to have one-on-one conversations with each beta tester. We'll be reaching out to each of you to schedule a follow up session, we'll most likely begin this process in early October.
III) Reporting Issues back to You
Click this link to see a list of reported issues. By providing you transparency we hope to eliminate redundant issue reporting, this will save both you and us time.