More detailed labels / on-hover text

[Cervator]

I mentioned earlier it might be an idea to add a label to the IRC button area suggesting the user stays in the channel for a while, since we often have people unfamiliar with IRC show up, ask their question (or even just ask if they can ask their question), then leave after a minute or less with no reply

Next day another example presents itself (MovingBlocks/Terasology#1100) with an issue filed here with our favorite of all time problem: Intel HD Graphics in a laptop that won't run the game. Maybe akin to how you can put a CONTRIBUTING file in a repo and you'll get a link when filing a new issue we can highlight reading that first as a note in the crash reporter

... naturally we still need to actually write such a file: MovingBlocks/Terasology#463 - but with this in mind maybe we can highlight a "common issues" section with some steps to try if you crash from something likely related to graphics, along with being sure to post your system specs in the issue.

Persistent labels might clutter the simplistic UI, maybe on-hover text (pop-up or dynamic display in an empty area) would be a better alternative

Maybe the pastebin button could show a "You'll get a link to copy paste after clicking this button" message just so all three show something

This is probably low priority if it seems worth doing at all :-)

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2091922-more-detailed-labels-on-hover-text?utm_campaign=plugin&utm_content=tracker%2F1626462&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1626462&utm_medium=issues&utm_source=github).

[msteiger]

We could also add a new tab "Known Issues" and hope that people look at it, before they file new issues. It would probably be good to have it online (in the Wiki maybe?) and download it on demand. Both Markdown and HTML should work fine. What do you think?

[skaldarnar]

In the wiki (using the new features by github) and then pull the pages to display in the Crash Reporter sounds like a good plan to me.
Would it make sense to provide a link to the list of open issues taged with »bug« so that users won't file new issues if there is already one?

[Cervator]

Sounds good to me, if it isn't too much effort for too little likely usage

Known issues should probably be a human friendly yet still automated version populating out of the issue tracker. Akin to the idea of "prettifying" commit logs for changelogs - auto-pull appropriate issues to a wiki page (or commits for a changelog) then allow a user to edit the descriptions. Even if nobody does at least there is still an accurate list of issues, with them being removed automatically when the issue is closed.

Jenkins could update the wiki lists when it runs normal builds

Probably a tad out of scope for this issue though, something to discuss in the forum sometime :-)