User Story
As a team, Reading Web would like consistent bug tasks in Phabricator, with clear issues and steps to reproduce, so that they can effectively engage with the bug and test properly.
Teams like iOS and Android have template links for submitting bugs and crash reports. These help the teams organize tasks and effectively triage, prioritize, reproduce, and fix bugs, by keeping Phab tasks consistent. Example:
https://phabricator.wikimedia.org/maniphest/task/edit/form/10/?title=[BUG]&projects=wikipedia-android-app-backlog&points=1&description=%3D%3D%3D+Steps+to+reproduce%0D%0A%23+%0D%0A%23+%0D%0A%23+%0D%0A%0D%0A%3D%3D%3D+Expected+results%0D%0A%0D%0A%3D%3D%3D+Actual+results%0D%0A%0D%0A%3D%3D%3D+Environments+observed%0D%0A**App+version%3A+**+%0D%0A**Android+OS+versions%3A**+%0D%0A**Device+model%3A**+%0D%0A**Device+language%3A**+
Acceptance Criteria
- Reading Web creates a link that prepopulates fields and information expected with each bug submission
- The link is placed on the Reading Web backlog board
Optional
- The link is provided via each Phab project for which the team is responsible, less sprintboards, and customized for each.