Last updated 18 March 2016.

This page describes the fields you will see when you create a new issue. If you are looking for guidance on how to best create an issue, the page Tips for making a good issue report has information on how to make your issue report as effective as possible.

Note that before you start, you should search the issue queue to see whether someone has already reported the same issue.

Note: Not all projects use all of the fields (for example, the Documentation project does not use the "version" field), and some fields are project-specific (e.g. "version" and "components"). The following table lists the fields you are likely to see, and describes what each one means.




The module, theme, translation, web site, or other component you are filing an issue against. In many cases, this is automatically selected.

Version (for some Project choices) Choose the current development version of the module, theme, or Drupal itself. Don't just pick the version you noticed the problem in. For more information, see Drupal's backport policy.
Component The area in which the issue affects the project. This will vary by project, as each project may choose their own list of components to present.


Category option list

A broad grouping of the kind of issue. Options are designated as follows:

  • Bug report is used for errors.

  • Task is used for things that should get done, but do not fit into another category.

  • Feature request is used when asking for new features that will enhance a project.

  • Support request is used when you need assistance using the project.

  • Plan is used when discussing the project roadmap.


Priority options list

The relative importance of an issue in relation to the project and other issues. See also Priority levels of Issues. The different levels of priority are defined as such:

  • Critical: This status is used to designate broken functionality that makes the project unusable.

  • Major: For issues which have significant repercussions, but do not render the whole system unusable.

  • Normal: This is the default priority applied.

  • Minor: You may apply this priority when there is no urgency to solve the issue.


Assigned Otpions List

The username of the person who is working on the issue. There are two different ways to fill out this field:

  • Unassigned: The issue has no one assigned to it. This is the typical setting for issues and is the default.

  • User (member name): A username of a member who is responsible for this issue.

Status Options List

The state, condition, class or current value of an Issue that describes a major stage in the document's life-cycle, and concerns. More details about setting a status can be found on the page Status settings for an issue.

Title Field

A descriptive heading for the issue.

Description Field

Descriptive text summarizing your request displayed with the issue title and provided with URLs when required from your query. The process of analyzing, organizing, and recording information that serves to identify, manage, locate, and explain your issue or post.

File attachments Files associated with this issue, such as screenshots, code snippets, or patches.

A non-hierarchical keyword or term to further categorize the issue. More detail about setting tags can be found on the page Adding tags to issues and using tags.