This ticket acts as a set of guidelines for the information you should try to put into a bug description, as well as some optional information that can be added after code review (i.e. diagnosis & notes for testing). It's written to be copy/paste-able (use the "view raw" option to get at the markup for easier pasting w/ formatting).
==== Ways to improve in this guideline
- [ ] Standard way to describe affected version(s) of the app
- [ ] Guidelines for how/when to include specific affected iOS version or device
- [ ] (For devs) a way to indicate when a ship was deployed (and to which channels)
= (Title) Frobnicator doesn't frobnicate on the fizzbuzz view.
//The ticket title should be a terse description of the bug. See [MW bug reporting guidelines](https://www.mediawiki.org/wiki/How_to_report_a_bug) for examples.//
== Steps to reproduce
# This should be a description
# Of the steps a tester executes
# To get to the point where expectations aren't met:
== Expected results
What's supposed to happen after the last reproduction step.
== Actual results
What actually happened on the last reproduction step. Screenshots, GIFs, screencasts, stacktraces, and OTRS tickets are worth a thousand (or more) words.