Template talk:Bug

an improvement?

would it be possible to make the bug template work a little more list like? or something I just see this page: trading_Post#Notes and think that instead of spamming the template we could have one bug then have bullets listing the others under it?- Zesbeer 23:56, 5 December 2012 (UTC)

easiest fix is to use <br> tags for newlines. adding bullets is awkward for the first line since it trims the damn whitespace. --Chieftain Alex 00:22, 6 December 2012 (UTC)

Most pages only have a couple bugs, it isn't really disruptive to the page either. However, it would make generating a dpl list of bugs plausible, so I'd support doing so.-Relyk 00:40, 6 December 2012 (UTC)

We can just restructure this so that bullets work as expected.

Bug.

No description given.

Bug.

• Test
• Test2

Now when you format the parameter with bullets, they work. The CSS margins might be off by a pixel or two, I didn't bother to scrutinize it all that much. —Dr Ishmael 00:49, 6 December 2012 (UTC)

We might as well push that change live. --Chieftain Alex 09:07, 6 December 2012 (UTC)

well I don't have the know how on how to do that. but I would. maybe add a {{bugs}}- Zesbeer 09:24, 6 December 2012 (UTC)

Updated. —Dr Ishmael 13:25, 6 December 2012 (UTC)

Bug 

Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world Hello world

Doesn't wrap correctly, with or without bullets.--Relyk 04:56, 17 December 2012 (UTC)

it is for me... what browser are you using ect?- Zesbeer 06:10, 17 December 2012 (UTC)

Fixed, regardless of browser. —Dr Ishmael 06:17, 17 December 2012 (UTC)

References

The <ref> tag fails when inside {{bug}}. Any way to fix it so that at least the reference notation can appear in-line with the bug note? 75.37.23.72 16:38, 29 May 2013 (UTC)

apparently SMW doesn't like ref. :/ -Chieftain Alex 17:01, 29 May 2013 (UTC)

I don't really understand why Relyk annotated this template in the first place. The bug value can be retrieved with DPL just as easily.

To the problem at hand, though, why do you need to use <ref> notation anyway? Just make it a plain external link. —Dr Ishmael 17:18, 29 May 2013 (UTC)

I think we should just get rid of the has bug attribute. It doesn’t really make sense to use it, especially when a single bug template call contains a list of bugs (for SMW multiple attributes should be set then). And we have the category anyway. Also SMW is known to have problems with longer text poke | talk 18:34, 29 May 2013 (UTC)

k--Relyk ~ talk < 20:24, 29 May 2013 (UTC)

Additional details, date added, severity, workarounds, developer acknowledgement

Maybe it's a good idea to have the date of when a bug was added to a page and the severity of a bug. It'd make a page like List of bugs a lot more useful to the community as there's currently a lot of bugs on there that are pretty minor, or from pretty old content. Making it hard to find some of the more severe bugs or currently relevant bugs.

I assume neither can be automatically added retroactively to existing bug notices, but it'd be nice information to have in the future. And you could of course manually add it to existing bug notices.

For the severity you would also have to figure out how to classify bugs, personally I'd maybe go with "Significant", "Major", "Minor", and "Aesthetic". Where a bug that prevents you from completing something would be Significant. A bug that often or always changes normal behaviour of gameplay content would be Major. A bug that only happens in specific circumstances or description mistakes (like misleading hints, etc.) would be Minor. And typos, wrong icons, missing flavour text, etc. would be Aesthetic. Of course these classifications are up to debate, even on a by bug basis.

It would also be nice if there was a way to make workarounds for bugs more visible in the bug notice. Currently it's just part of the text, making it easy to miss.

Additionally it would be nice if there was an optional section to a notice where you could mention if a bug has been acknowledged by Arenanet. For instance if the bug has been mentioned by a developer on the forums, or if it's mentioned in a support article.

I feel like these changes could help the community a lot in keeping track of bugs in the game, and making sure people know about the current status of it. Maybe the wiki doesn't want to be a full on bug tracker for the game, but having something like it could be a big boon to the game and currently there's not really a better resource out there than the list of bugs here on the wiki.

Generally agree with most of this, but deciding severity would be entirely subjective that I don't think would be worth adding. Adding acknowledgements you could technically do already just by adding references to the bug note.ItVictor (talk) 11:53, 16 April 2023 (UTC)

Date would be good, it doesn't even need to display on the page (e.g. |date=2023/04/16). For significant bugs however we have Template:Bug notice. -Chieftain Alex 15:10, 16 April 2023 (UTC)