When asking a question on Meta, you must include one of the four following required tags. This helps classify questions according to the type of response needed.
You've found an erroneous or unexpected behaviour in the system that needs to be fixed. Your question will include what you did to discover the bug, the steps required to reproduce the problem, the given system output, and the expected system output. If necessary to document or explain the issue, include a screenshot in your post. Liberal use of freehand circles is strongly encouraged.
You want to solicit opinions or best-practices on a particular topic, with the goal of reaching community consensus.
You have an idea for a new feature to be added to the Stack Exchange network engine. Your question will contain the details of your proposal, along with a justification that the new feature is needed.
You need help with the use of one of the network sites' features.
These tags can only be applied and removed by diamond moderators. They appear in red, not the usual gray, and confer a degree of official status.
Indicates that a post is an official poll for community ad selection. A moderator-only tag since July 19, 2011.
Indicates that a question is a part of the official Stack Overflow FAQ.
Marks a question for display in the Meta house ad on the Stack Overflow main page. This concept originated on per-site metas. Currently, when using it on Meta Stack Exchange, it makes the question show up on the sidebar on all sites.
Indicates that a submitted issue is actually due to the existing design of the system and is not considered erroneous behaviour. In other words, "it's not a bug, it's a feature!"
Indicates that a feature request has been implemented, a bug has been fixed, or another type of request has been processed.
Indicates that a request (usually a feature request) has been considered, but will not be implemented.
Indicates that the issue will be reviewed in the future.
Indicates that a reported erroneous behavior cannot be reproduced by the development team.
Indicates that a feature request has been considered and received positively enough that its implementation has been placed in the development queue.
Indicates that the symptoms of a bug report have been reproduced/confirmed by the development team.
Indicates that a feature request or possible solutions to a bug are set to be internally reviewed.