Closed
Description
Feature Issue
We are receiving a lot of empty user error reports without any details, so will be nice to ask users for feedback in more user-friendly format to receive meaningful feedback.
Description
Currently on shaking phone dialog is shown and on tapping "Report a bug" long template is shown.
Let's ask users at least for some feedback and paste it into description.
Also IMO template is too complicated
1. Issue Description
(Describe the feature you would like, or briefly summarise the bug and what you did, what you expected to happen, and what actually happens. Sections below)
2. Steps to reproduce
(Describe how we can replicate the bug step by step.)
-Open Status
-...
-Step 3, etc.
3. Expected behavior
(Describe what you expected to happen.)
4. Actual behavior
(Describe what actually happened.)
5. Attach screenshots that can demo the problem, please
Acceptance Criteria
Simplified version of user report inside app.
We can add fields, i.e.:
- description
- steps (not required)
And after that open mail client with pre-filled info.
Would appreciate some thoughts from UX and design side (@hesterbruikman @errorists )