This page describes the fields you will see when you create a new issue (the How to make a good issue report page 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 that if you click on a generic create a new issue link, the first thing you will need to choose is the Project to file the issue in. If you click on a Create a new issue link when you are already viewing a specific issue queue (such as the issue queue for a particular project), this will be chosen for you.
Once you have chosen the project, you will see a form with most or all of the following fields. Not all projects use all 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 will see, and describes what each one means.
|
Field
|
Description
|
|
Project
|
Project definition:
The module, theme, translation, web site, or other component you are filing an issue against.
Project Options:
- If you have an issue with a contributed module, theme, translation, or installation profile you downloaded from drupal.org, select it from the list.
- Select the "Documentation" project if you have found an issue related to information on a Handbook page on drupal.org.
- Select the "Drupal" project if you are reporting a problem with the core parts of Drupal, or with some documentation you found on api.drupal.org (which is embedded in the Drupal core code).
- Select "Drupal.org web masters" for page delete requests, such as Spam and test handbook pages.
|
| Version (for some Project choices) |
Choose the version of the module, theme, or Drupal itself where you noticed the problem.
|
| Component |
Definition: which area of the project the issue effects. This will vary by project, as each project may choose their own list of components to present.
If you are reporting an issue against the Documentation project, the Documentation issue reports page has information about how to choose the component. For other projects, choose a component that conforms most closely matches the problem you are seeing. |
|
Category default: 
Category options:
|
Category definition:
a broad grouping of the kind of issue. If you are reporting an issue in the Documentation project, see the documentation descriptions as they are slightly different from most projects.
Category Options:
-
"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 for use when you need assistance using the project.
|
|
Priority default:
Priority options:
|
Priority definition:
The relative importance of an issue in relation to the project and other issues. See also Priority levels of Issues
- Priority options:
-
Critical: This status is used to designate broken functionality that makes the project unusable.
-
Normal: This is the default priority applied.
-
Minor: You may apply this priority when there is no need to harry about the issue.
|
|
Assigned default: 
Assigned options: 
|
Assigned definition:
the user name of the person who is working on the issue.
- Assigned Options
-
Unassigned: the issue has no one assigned to it. This is the typical setting for issues and is the default.
-
User(member name): As a registered Drupal.org user you will see that your username will appear in the select list. You should only select your name only if you want to take responsibility for seeing the issue to completion, or to its next step towards completion. Be sure to unassign the issue when you are done working on it.
|
|
Status default: 
Status options: 
|
Status definition:
The state, condition, class or current value of an Issue that describes a major stage in the document's life-cycle, and concerns. Each Drupal.org issue has a status assigned so that we can tell at a glance what progress has been made with each issue. See also Status levels of issues. The documentation issue reports page explains how the documentation queue uses statuses.
|
|
Title field
|
Issue Title definition:
A descriptive heading for the issue.
|
|
Description field
|
Description definition:
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. Read the How ot make a good issue report page for more information.
|
| File attachments |
You can attach files to your issues here. These can be screen shot images, files that would be useful for a developer trying to reproduce the issue, supplementary information, or patches. You can also attach files to comments on issues. |
| Tags |
You can freely type any tags to add information to your issue. However, tags are most useful if they are used by multiple issues, because people can click on a tag to find other issues marked with that same tag, and they can also use Advanced Search to search for issues by tag. So, when using tags, try to choose tags that others have already used (which you will see as you begin typing your tag).
Some commonly-used tags:
- Novice: Issues that someone new to Drupal could help with (easy to make a patch for)
- ui-text: Issues involving updates to user interface text
- Help text: Issues involving updates to help text within Drupal
- API change: Issues involving changes to the Drupal API
- Markup change: Issues involving changes to HTML tags and attributes that are generated within Drupal (as opposed to the text within the HTML)
- The Documentation issue reporting page lists the tags that are specific to documentation issues.
|
