Last updated 2 January 2014.

On this page you find a couple of suggestions for improving the likelihood of an issue report getting attention from a developer.

Helping the developers

Helping in a few straightforward ways to reduce developers' workloads can better enable (as well as motivate) them to help you. The following points can make an unexpectedly significant difference.

Improving the issue description

Many issue reports don't get attention because the quality of the report is low. Well written reports can be addressed more efficiently by developers. Complete reports contain items such as

  • easy-to-read issue summaries (template), especially at the top of long issue discussions,
  • clear steps for reproducing the issue,
  • comprehensive information with status, version, priority, and other values set correctly and objectively (if necessary, ask the original reporter for more information).

Try to repeat the problem yourself and note any differences or similarities in the results and the system configurations. Reports that multiple users have been able to reproduce the issue are helpful.

Providing a patch

Sometimes the bug report already contains a description of the solution or the code for fixing the bug. You can use this information to create a patch. While it may seem trivial, a patch makes the developer's job easier.

Reviewing, testing and improving an existing patch

Sometimes the bug report already contains a patch. Reviewing, testing and improving it can remove hurdles to having the patch committed.

  • Review the patch for compliance with Drupal's coding standards.
  • Test it. Apply the patch and check that it successfully resolves the issue without introducing new issues. Two things to remember when testing: before applying the patch, verify and take notes on the issue so you can reliably identify the changes; if the patch applies successfully and resolves the issue, remember to mark it as "reviewed and tested by the community (RTBC)."
  • Reroll patches that have sat around too long and no longer apply.

Although these items can be challenging if you are not already proficient with Drupal, attempting them can help you better understand how Drupal works. If you're not confident in your results, don't hesitate to post them and invite others to provide feedback.

Writing tests

Much of Drupal's framework is using tests to automate checking for problems. Write tests to help developers ensure their code works.

Hiring someone or providing a bounty

Sometimes it helps offering money to get the error fixed. Putting out some money on a bug (or getting others to join together to create a big bounty) can result in the quick resolution.

The Marketplace of Professional Services lists Drupal service providers available for hire. You can also read the HowTo: Hire a Drupal site developer to help you in finding the right person.

Tempting things that don't help (and might hurt) the process

  • Do not assign a higher priority than your issue objectively deserves.
  • Do not "bump" your issue.