The apps team is starting a practice of having required information on a bug ticket to enable our team members to estimate and reproduce bugs more reliably.
We documented these requirements here:
To share this with the rest of the organization and to better support the entry of specific data, we would like add some or all of these requirements as separate fields in Phabricator tasks.
The new fields (taken from the document above) would be:
- Observed Behavior
- Expected Behavior
- Steps to Reproduce
It wold be nice to hear other contributors thoughts on the above document and proposed fields to see if this is something others in the organization would want, and what fields they think should be added.
This task may require that there are different ticket types (feature, bug, story, epic) before it can be implemented. For instance, we may not want these fields visible on feature tickets.