01
Provide a reproducible report
Include the app version, operating system, device model and the steps leading to the issue. Describe whether it affects all users or a particular account or workflow. Share screenshots or logs only after removing private information and access tokens.
02
Check related services
If the issue involves login, notifications, payments or another integration, identify the affected workflow and record the relevant non-sensitive reference. Tell the team about recent API, configuration or third-party changes.
03
Prepare an agreed release checklist
Before a release, agree which user journeys must be tested and who approves the build. Confirm the release destination, required business-owned accounts and any handover steps. Store submission and approval timing depend on the relevant platform.
04
Scope product changes separately
For a new feature, describe the users, screens, permissions and outcome. The team can review dependencies, acceptance criteria and the required quote before work begins. Avoid mixing a fault report with an unapproved expansion of the product scope.
Your next-step checklist
- App version and device recorded
- Reproduction steps and impact described
- Shared files cleared of credentials
- Release approval and feature scope agreed
Put this guide to work.
Tell us about your goals and current setup. We can help you discuss the requirements and plan a suitable next step.
Discuss your project