Moovs makes it easy to submit detailed issue reports directly to our product team. Start by logging into Moovs and click on the question mark icon on the lower right corner of the screen. From there, scroll down and select "Issue Report"
Understanding the Issue Report Form
A well-structured issue report form typically includes fields to categorize, prioritize, and describe the problem in detail. Let's break down the common sections:
Category: This helps classify the type of issue (e.g., Flight Aware, SMS Delivery, Email Delivery, Other).
Priority: This indicates the urgency and impact of the issue (Low, Medium, High).
Expected Behavior: What should have happened according to the application's design or your understanding.
Actual Behavior: What actually happened when the issue occurred.
Steps to Reproduce: A clear, step-by-step guide on how to trigger the issue, allowing others to experience it themselves.
Steps to Submit a Comprehensive Issue Report
When you encounter a problem, take a moment to gather your thoughts before filling out the form:
Select the Category:
Click on the "Category" dropdown.
Choose the most appropriate category that describes the nature of the problem you're reporting. This helps route your report to the correct team.
Set the Priority:
Consider the impact of the issue.
Low: Minor inconvenience, cosmetic issue, or something with a workaround.
Medium: Affects some functionality but doesn't halt critical tasks, or has a temporary workaround. (As highlighted in the screenshot, "Medium" is the default or selected option).
High: Prevents you from performing essential tasks, causes data loss, or impacts a large number of users.
Select the priority that best reflects the severity of the issue you're facing.
Describe the Expected Behavior:
Clearly state what you anticipated would happen. For example, "I expected the image to upload successfully and display in my gallery."
This sets the baseline for understanding why the actual behavior is problematic.
Describe the Actual Behavior:
Be precise about what went wrong. For example, "The upload progress bar froze at 50%, and the image never appeared in my gallery."
Include any error messages you received or unusual symptoms you observed.
List the Steps to Reproduce:
This is arguably the most critical part of an issue report. Provide a numbered list of actions that consistently lead to the problem.
Start from a known state (e.g., "1. Log in to the application. 2. Navigate to the 'Profile' section.").
Be exhaustive. Include every click, input, and navigation step.
Example:
Open the application.
Go to the "Settings" menu.
Click on "Change Password."
Enter the new password in both fields.
Click "Save."
Then state the actual behavior based on these steps.
Finalizing and Submitting Your Report
Review: Before submitting, quickly reread all the fields to ensure clarity, accuracy, and completeness.
Submit: Click the "Submit Report" button.
Cancel: If you decide not to submit or need to rethink, click "Cancel."
By taking the time to fill out each field accurately and thoroughly, you significantly increase the chances of your issue being understood, replicated, and resolved quickly by the development team. Your detailed reports are a key contribution to improving the product for everyone.