Issue Submit Form - Description Table

Submit form Title

Form Title

Projects List field:

Project definition:
_{Means the project or projects described or listed. Generally, an organized set of activities more narrowly directed toward a common purpose. (i.e. Project types).}

Project Options:

• _{Use "Documentation" for most handbook documentation issues.}
• _{Use "Drupal.org web masters" for page delete requests, such as Spam and test handbook pages.}

Component default:

Component options:

Component definition:
_{a smaller, self-contained part of a larger entity.}

Component Options:

• Correction/Clarification:
  _{This is for existing documentation. If documentation is unclear or wrong, please choose this component. For example, content is actually wrong and needs to be updated or something is just blatantly confusing.}

• New Documentation:
  _{If you have suggestions about adding documentation, either sections or content, please use this component.}

• Placement and Navigation:
  _{Content should be moved to a different section because it would be more relevant there.}

• Delete Comments:
  (new description?)

• Outdated:
  _{If content is outdated and does not apply or should be found under a different section/archive, use this component.}

• Vandalism/Spam:
  _{If content or comments are vulgar or Spam, let us know by using this component.}

• Join Documentation Team:
  _{If you are confused on how to join the Documentation Team, or are having trouble regarding this topic, please use this component. Please make sure you have read the documentation on Joining the Documentation team here [link here]}

• Other Documentation Issues:
  _{If for some reason, your issues does not fall into the preceding component categories, please use this one.}

Category default:

Category options:

Category definition:
_{A Category is the name for a collection of content items that are related in some way. Example: The category 'Fish' may contain the Content Items 'Herring', 'Haddock' and 'Stickleback'. Category is part of the Content hierarchy.}

Category Options:

• "bug report":
  _{is used for errors. See Bug reports for documentation on submitting issues against modules. See Embedded documentation for submitting issues on the built-in help text.}

• "feature request":
  _{is used for requests, including new material and policy changes.}

• "tasks":
  _{is used when an update is in development.}

• "support requests":
  _{is used for requests that require site administrator role, including joining the documentation team, deleting handbook page comments that have been incorporated, and adjusting page weight for proper page ordering.}

Priority default:

Priority options:

Priority definition:
the relative importance of a task in relation to other tasks.

Priority Options:

• Critical

• Normal

• Minor

Assigned default:

Assigned options:

Assigned definition:
_{the user name of the person who is working on or needs to give attention to the issue. Appointed to a post or duty; "assigned personnel"; "assigned duties"}

Assigned Options

• Unassigned

• User(member name)

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.}

Status Options:

• active: _{(Dev.) No patch is attached to the issue. (Doc.) (to be defined)}

• active (needs more info):
  _{There is insufficient information in the issue to proceed.}

• patch (code needs review):
  _{abbr. CNR (Dev.) A patch has been created and needs review and testing. (Doc.) (to be defined)}

• patch (code needs work):
  _{abbr. CNW (Dev.) The patch needs additional work before it should be reviewed. (Doc.) (to be defined)}

• patch (reviewed & tested by the community):
  _{abbr. RTBC (Dev.) The patch has received a thorough review and test by one or more experienced developers. (Doc.) (to be defined).}

• patch (to be ported):
  _{(Dev.) The patch has been committed to a branch of the project. (Doc.) (to be defined)}

• fixed: _{(Dev.) The issue has been resolved (usually by committing a patch). (Doc.) (to be defined).}

• duplicate:_{A similar issue has already been created.}

• postponed: _{The issue seems like a good idea, but other (often related) issues need to be dealt with first.}

• won't fix: _{It has been decided that this issue will not be fixed.}

• by design:_{(Dev.) The raised issue has been deemed not to be an issue. (Doc.) (to be defined).}

• closed: _{The issue is no longer current.}

Title field

Issue Title definition:
_{A general or descriptive heading for a section of a written work.}

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.}

_{When the issue are related to Discussions, amongst the Documentation maintainers (Doc-Team) (via an issue report) you should always file an issue prior to performing the following types of changes:}

1. _{Changing the name of a top level chapter in one of the books.}
2. _{Moving a top level chapter in a book.}
3. _{Large re-writes.}
4. _{Big re-organizations.}
5. _{Rough drafts that are not yet ready for production.}