If commits reference a given issue, cross-post them to the issue so they're visible in the comment stream.
Provide the ability to create first-class forks / sandboxes of parent projects and perform pull requests, tightly integrated with the canonical project/repository.
Allow modules, themes, sandboxes, etc to act more like 'Groups' in which an issue queue is only one aspect of them. Modules could have discussions, wiki pages, events, and could help potentially help tie in the work being done with initiative pages. Functionality like maintainers being able to send out e-mail announcements (i.e. Broadcast) to people 'subscribed' to a module with security releases or major features. This ...more »
Allow individual issues to be turned into Git repositories, which allows everyone working on an issue to collaborate in one spot.
Provide an alternate project_issue view for maintainers so that they can make bulk changes to things in their queue (e.g. re-componentize, tag, apply status changes, etc.)
'Topic' page aggregates all activity across d.o for a given topic, to make finding related information and activity much easier. The purpose of the 'topics' is multiple including: - a way for people to identify their expertise - a way to aggregate content of interest to that topic from across Drupal.org - a way to see what is happening around specific topic right now, where and who is active - a way to aggregate people ...more »
We have a host of community initiatives, where members in the community get an itch, identify the most important issues that relate to their initiative, and call them out. See for example Accessibility or the HTML 5 initiatives. These initiative pages were invaluable during Drupal 7 code thaw for rallying people around various development efforts. However, they have a number of problems: * Each initiative is captured ...more »
The Component property of an issue is a single value currently. Often times, however, an issue spans over multiple components/topics, in which you have to figure out the primary component and usually assign the other ones as issue tags. Especially for Drupal core, an issue might be related to Node module, but is also changing plethora of CSS, JS, and markup. And oh, that very same issue might even try to "fix" an oddity ...more »