>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3581762. --> Reported by: [heatherwoz](https://www.drupal.org/user/694068) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>There are many feature requests and bug reports for the Drupal.org Community Events section scattered across the <a href="https://www.drupal.org/project/issues/drupalorg">Drupal.org customizations issue queue</a> and <a href="https://www.drupal.org/project/issues/event_organizers?categories=All">EOWG issue queue</a>. It is hard to get an overview of all event-related issues for planning and prioritization.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Visit either queue and attempt to find all relevant issues. Searching for "community events" or "events" brings up items that are not necessarily related to the community events section.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Review both issue queues.</li> <li>Move issues that are about changing events or the community event section on Drupal.org to a single queue and tag them consistently. (After consulting with @drumm, decided to move them to Drupal.org customizations project since that is where they need to be for DA team to review/approve/act on them and for MRs to be submitted. We are tagging them all with "Community Events" component, which will become a label when issues are migrated to Gitlab.)</li> <li>Close outdated or fixed issues.</li> <li>Close duplicate issues.</li> <li>Inform event organizers that everything is now organized in one place (<a href="https://www.drupal.org/project/issues/drupalorg?text=&amp;status=Open&amp;priorities=All&amp;categories=All&amp;version=All&amp;component=Community+events">Community Event issues</a>) so they can continue to comment and discuss on the issues.</li> </ul> <h3 id="remaining-tasks">Remaining tasks</h3> <p>None.</p>