Write proper tickets: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
With the following pattern you can easily write more comprehensible and clear tickets like bug reports and change requests. Just copy/paste it. It includes Wiki Markup for proper styling, please make sure to keep the linebreaks between headlines and copy. | With the following pattern you can easily write more comprehensible and clear tickets like bug reports and change requests. Just copy/paste it. It includes Wiki Markup for proper styling, please make sure to keep the linebreaks between headlines and copy. | ||
Steps to reproduce | Steps to reproduce | ||
How/where can i reproduce? An url/path including url to help the assignee reproduce what you experienced | How/where can i reproduce? An url/path including url to help the assignee reproduce what you experienced | ||
Revision as of 07:56, 11 September 2019
Write proper tickets
With the following pattern you can easily write more comprehensible and clear tickets like bug reports and change requests. Just copy/paste it. It includes Wiki Markup for proper styling, please make sure to keep the linebreaks between headlines and copy.
Steps to reproduce How/where can i reproduce? An url/path including url to help the assignee reproduce what you experienced Actual result Current functionality. A short description what currently happens (what should not happen). Expected result Expected functionality. A description what you expect to happen. Often it’s the above sentence reversed (even if this sounds wired, it's super helpful...). Environment Browser, OS, Mobile, Desktop, Stage, Live, describe the environment, where this result can reproduced to help the assignee to reproduce the wrong behavior.