Templates for issue status changes

This page contains suggested text that you can use (possibly with modifications) when you update a project issue from one Status value to another. Here is a partial diagram of common transitions – but note that the “Reviewed and tested by the community” state is missing from the diagram:

Comment templates for changes in Status

All new issues

Thanks for taking the time to report this issue.

=> Fixed

Thanks for reporting, reviewing, and testing! Committed to all branches.

A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.

=> Fixed (Support request too specific)

Sorry, but this request is too custom/specific to be handled by the maintainers of this project.

There are several support options listed if you click on Resources > Support at the top of Drupal.org, which will take you to  https://www.drupal.org/support

There you can find out about the Drupal Slack channels, and the Forums, which are our two main support mechanisms in the Drupal community.

Good luck with your issue!

=> Fixed (Support requests in Drupal Core queue)

I'm sorry, but although you can create issues in Drupal Core and mark the category as "support request", we don't really handle support requests in the Drupal Core issue queue as a regular practice (that option is mostly there for filing support issues for contributed modules and themes).

There are several support options listed if you click on Resources > Support at the top of Drupal.org, which will take you to  https://www.drupal.org/support

There you can find out about the Drupal Slack channels, and the Forums, which are our two main support mechanisms in the Drupal community.

Good luck with your issue!

Needs more info => Closed (cannot reproduce)

Sorry, without further information this issue can only be closed as not reproducible.

Feel free to re-open this issue if you want to provide further information. Thanks.

==> Won't fix (feature requests)

At this point, this issue is going to be marked as won't fix. This is either not in the direction of the project, or too out of the project scope.

==> Won't fix (co-maintainer application)

Hi, and thank you for volunteering!

However, I may be mistaken, but I don't think I've seen any contributions from you to this project yet. So at this point, I can only recommend to read <a href="http://drupal.org/node/363367">best practices for co-maintaining projects</a>

Thanks!

=> Duplicate

Thanks for taking the time to report this issue.

However, I am marking this as a duplicate of [#]. You can follow up on that issue to track its status instead. If any information from this issue is missing in the other issue, please make sure you provide it over there.

If you are new to drupal.org, it would help us if you would search for existing issues before submitting a new one. We strongly advise you search using the drupal.org search facility, because it really is very good. NOT a third party search engine (e.g. Google) as you may well not find what you are looking for.

==> Postponed

This issue needs revisiting, with the potential to be added to the project later. Please feel free to contribute additional information or patches.

==> Postponed (waiting for another issue)

This issue cannot proceed until this blocker issue is resolved: [#] 

==> Active (for duplicate projects)

The <a href="http://drupal.org/project/X">X</a> module provides a very similar feature to this module.

One of the <a href="https://www.drupal.org/about/mission-and-principles">7 principles of the Drupal project</a> is collaboration. Would you consider merging your project into that one and collaborating with its authors?

Otherwise, it would be great if you could document what makes this module different so that people can make a good decision about which one to use.

==> Closed (outdated)

This version of X is not supported anymore. The issue is closed for this reason.

Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

==> Closed (when someone reopens an issue that was long-since fixed)

Thanks for taking the extra step and looking for a pre-existing issue.

However, since this issue was previously marked closed/fixed, we should leave it closed and start a new issue. The only reason for reopening a fixed and closed issue is if the fix is incomplete or causes new problems.