Suggestions for improving the d.o issue queue (especially for core)

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

This page is a place to gather suggestions to improve the drupal.org issue queue (provided by the Project issue tracking module), especially as relates to the core issue queue (by far the largest and most active queue on the site). Please add to the list, or edit items to provide a link to the corresponding issue (feature request, whatever) in the project issue queue.

Note: Requests to add or rename issue status values belong in the drupal.org webmaster issue queue (component == 'Site organization') since those are just admin settings on d.o, not hard-coded into project_issue.module.

Mentioned on the devel list:

  • Add "concept needs feedback" status for earlier discussion of architecture.
  • Close "active (needs more info)" after two weeks: see issue Dealing with "active (needs more info)" issues.
  • Add "patch - needs benchmark" status.
  • Better support for per-component maintainers:
    • Automatically assign issues to the component maintainer?
    • RSS feeds per component
  • Ability to re-assign tickets to someone else. http://drupal.org/node/4354
  • Way to "subscribe" (add it to your tracker/my issues page, and/or email) without actually following up to the issue. http://drupal.org/node/34496
  • Convert issues to comments. http://drupal.org/node/18920
  • Rename the current "patch (ready to be committed)" to "patch (ready for final review)". Issue: http://drupal.org/node/156637
  • Add a description to the Issue Information fieldset that links to handbook pages describing the meaning of the fields and the Drupal development process. See issue #159457.
  • The "web of trust" be formalized and those developers get a new permission to upgrade an issue from "patch (ready for final review)" to a new, restricted "patch (ready to be committed)" status. (this is already supported by project* module)
  • Patches that are not marked "code needs work" or "to be ported" be periodically and automatically checked to make sure they still apply without FAILing.
  • Improvements to advanced search:
    • Make it easier to find in the first place
    • Selecting in small multi-selects is a pain, perhaps checkboxes are better?
    • Selecting all issues for a given series (5.x, 4.7.x), not just specific versions. http://drupal.org/node/97569
    • Should defaults include support requests?
    • Layout the table more nicely.
    • A little bit of descriptive text could help get new users up to speed faster, but not get in the way of power users.
    • Land on the URL currently marked by a # on the results page.
  • Improvements to the results page:
    • Getting a specific url for it requires knowing to click the # hidden at the bottom. We should go directly to the permanent link.
    • The dropdowns are inadequate to represent your search and are often wrong. A full description of the search should be shown, even if it is not editable. The dropdowns should probably be skipped all together. [note: I partially disagree with this. The dropdowns should be improved to represent the search, but I find it incredibly useful to be able to further refine a search by tweaking the drop-downs in this case]
    • There is no way to get to a pre-filled advanced search screen from your current results. Making minor adjustments to the search is impossible, unless you are lucky enough to have it in your browser history.
    • A line saying how many issues were found would help with tracking progress.
  • A 'decay feature' that sets a patch back to 'code needs review' after 2 weeks as RTBC?: won't fix.
  • Various proposals for voting on moving status values, etc. [note: This seems doomed, that it will generate more work than it'll solve, etc. This has no support, so I'm not bothering with an issue about it.]
  • somebody mentioned it before, but let's make sure it's counted: a way to perform some mass operations on the results of the search page. like mass changing the status of issues, or mass assigning/unassigning.
  • AJAX teasers for issues
  • drupal.org infrastructure needs to scale so that using the issue queues is not so slow and painful.

Some of my other suggestions:

  • Provide a way to "show all", or "show X results per page" on the pager results.
  • E-mail issue subscribing should be more visible. http://drupal.org/node/16014

Moshe's suggestions:

  • add some checkboxes to a followup which indicate the quality of the patch review:
    -- i tested the functionality
    -- i reviewed the code for standards compliance
    -- i reviewed the code for elegance
    -- i agree with the proposed functionality
  • let people register thumbs up or thumbs down without generating a full followup or an email notification http://drupal.org/node/42232
  • Way to subscribe to dev releases. If an issue has 200 posts then a dev release, testers want to know there is something to test without following the whole discussion.

Issue tracking and software releases

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week