Adding tags to issues

Last updated May 18, 2013.

Project maintainers use the field "Issue tags" of the issue to classify or group related issues so they can deal with bugs effectively.

They are not intended for end users. Maintainers use them to classify posts .

General guidelines

• If you must use a tag, please choose from among the ones listed here:
  • Special issue tags
  • Topical issue tags
  • Documentation issue tags
• Don't create a new tag, unless you are the project maintainer or have been asked to. Select one of the existing options instead, if appropriate.
• Don't use terms that appear in the hard-coded issue fields as component, assigned, priority, status, or title.
• Check your spelling and formatting carefully to ensure you're not inadvertently creating a new tag.

Project maintainer guidelines

You can use tags for:

• Tracking issues for initiatives that span multiple projects. E.g. git phase 2 or drupal.org redesign
• Grouping issues within a single project that span multiple components. E.g. core's usability issue queue
• Classifying issues with more detail than the status, especially defining what exactly "needs work". E.g. needs tests or needs documentation
• Tracking "milestones", e.g. the Project module's 6.x-1.0 blocker issue queue or issues targeted for implementation during git sprint 4
• Classifying issues by other criteria than the hard-coded default fields. For example:
  • Defining how difficult certain issues are expected to be, e.g. novice issues
  • Tracking (and at times debating) if an issue qualifies as an API change, if it
    breaks the string freeze, etc
  • Classifying an issue as FAQ when another issue is closed as a duplicate of it