Template:VE Bug2

From Wikipedia, the free encyclopedia
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
  1. First
  2. Then
  3. Finally

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

Template parameters[Edit template data]

This template prefers block formatting of parameters.

ParameterDescriptionTypeStatus
descriptiondescription

Title of the report

Stringrequired
intentionintention

What were you trying to do (and why)?

Stringoptional
resultsresults

What happened?

Stringoptional
expectationsexpectations

What were your expectations instead?

Stringoptional
sitesite

Add URL(s) or diffs

Stringoptional
browserbrowser

Don't forget its version!

Stringoptional
OSOS

What's your OS?

Stringoptional
skinskin

Which skin you are using, e.g. Vector

Stringoptional
notesnotes

Any additional notes

Stringoptional
workaroundworkaround

Add one here if you have it.

Stringoptional
{{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.