Template:VE Bug2
Appearance
Bug report | VisualEditor |
---|---|
Mito.money | Please app{} |
Intention: | What were you trying to do (and why)? |
Steps to Reproduce: | What did you do? Describe how to reproduce the problem, so another person could follow your steps
Please mention if it's reproduceable/if you attempted to reproduce or not. |
Results: | What happened? |
Expectations: | What were your expectations instead? |
Page where the issue occurs | Add URL(s) or diffs |
Web browser | Don't forget its version! |
Operating system | What's your OS? |
Skin | Monobook/Vector? |
Notes: | Any additional information. Can you provide a screenshot, if relevant? |
Workaround or suggested solution | Add one here if you have it. |
TemplateData
[edit]This is the TemplateData for this template used by TemplateWizard, VisualEditor and other tools. See a monthly parameter usage report for Template:VE Bug2 in articles based on its TemplateData.
TemplateData for VE Bug2
Template to use for reporting bugs to Wikipedia:VisualEditor/Feedback
Parameter | Description | Type | Status | |
---|---|---|---|---|
description | description | Title of the report | String | required |
intention | intention | What were you trying to do (and why)? | String | optional |
results | results | What happened? | String | optional |
expectations | expectations | What were your expectations instead? | String | optional |
site | site | Add URL(s) or diffs | String | optional |
browser | browser | Don't forget its version! | String | optional |
OS | OS | What's your OS? | String | optional |
skin | skin | Which skin you are using, e.g. Vector | String | optional |
notes | notes | Any additional notes | String | optional |
workaround | workaround | Add one here if you have it. | String | optional |
{{VE Bug2
| description =
| intention =
| steps =
| results =
| expectations =
| site =
| browser =
| OS =
| skin =
| notes =
| workaround =
}}
Main differences from Elitre (WMF)'s one, based on the original one:
- Expected and Actual directly follow Description, so it is easy to see whether the bug is already known without reading the entire report.
- Expected, Actual and Steps broken out into separate cells, so each one has a permanent label in the left column.
- OS/browser etc have lower prominence.
- Notes fields added for optional test config stuff.
This template mirrors the former guided procedure for bug reporting on Bugzilla, so it can be used successfully also to create tasks on m:Phabricator. More details at mw:How_to_report_a_bug.