>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3563282. --> Reported by: [afoster](https://www.drupal.org/user/594458) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>Request for Starforge board for the AI UX team.<br> <strong>Check-in Date: </strong>12/15/2025<br> <strong>Additional Collaborators: </strong>Aidan Foster, Emma Horrell, Christoph Breidert<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The AI UX team's work is currently spread across multiple issue queues (the main AI Initiative project, AI Core and various contrib modules). This makes it difficult to get a consolidated view of all UX-related tasks, which hinders our ability to prioritize work and provide transparency to the community.</p> <p>To effectively manage our workflow and backlog, we need a single dashboard that aggregates all relevant UX issues.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Please create a new Kanban board on Drupal Starforge titled "AI User Experience Team".</p> <p>This board should automatically pull in and display issues that meet the following criteria:</p> <ul> <li>Any issue in the <strong>Drupal AI Initiative</strong> project where the <strong>Component</strong> is set to <code>UX</code>.</li> <li>Any issue from any of the tracked AI modules that has the tag <code>Needs UX review</code>.</li> </ul> <h3 id="summary-kanban-board-logic">Kanban Board Logic: Mapping Drupal.org Statuses to Swimlanes</h3> <p>This matrix defines the criteria for how Drupal.org issues will be automatically sorted into the AI UX Team's Kanban board swimlanes. This logic can be used to configure a Drupal Starforge board.</p> <p><strong>Universal Board Filter:</strong> All issues on this board must first meet the following criteria:</p> <p><code>(Tag = Needs UX review) OR (Component = UX in the AI Initiative project)</code></p> <p>A "Show Meta Issues" checkbox will also be available on the board to allow users to toggle the visibility of meta issues.</p> <table> <thead> <tr> <th>Kanban Swimlane</th> <th>Drupal.org Status</th> <th>Assigned To?</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td><strong>UX Intake</strong></td> <td><code>Active</code> OR <code>Needs review</code></td> <td>Unassigned</td> <td>The entry point for all new work. An unassigned issue with either status is waiting for initial triage by the review team.</td> </tr> <tr> <td><strong>UX Ready for Work</strong></td> <td><code>Needs work</code></td> <td>Unassigned</td> <td>A prioritized backlog of issues that have been triaged, validated, and are ready for a UX team member to assign to themselves.</td> </tr> <tr> <td><strong>In Progress</strong></td> <td><code>Active</code></td> <td><strong>Assigned</strong></td> <td>An issue that is actively being worked on by a specific team member. An <code>Active</code> status with an assignee signifies work is underway.</td> </tr> <tr> <td><strong>Review</strong></td> <td><code>Needs review</code></td> <td>Assigned</td> <td>The UX work (e.g., design, documentation, MR) is complete and ready for feedback. <strong>The assigned person is responsible for presenting the issue for final approval during the weekly Monday sync meeting.</strong></td> </tr> <tr> <td><strong>Done</strong></td> <td><code>Closed (fixed)</code><br><code>Closed (won't fix)</code><br>(etc.)</td> <td>Any</td> <td>The issue is considered complete and no further action is needed from the UX team.</td> </tr> </tbody> </table> <h3>Key Workflow Notes</h3> <ul> <li><strong>Dual Entry for Intake:</strong> The intake process funnels two types of issues for triage: community requests (via the tag) and internal projects (via the component).</li> <li><strong>Assignee is the Differentiator:</strong> The <strong>Assigned to</strong> field is the key that distinguishes between an "Intake" task and an "In Progress" or "Review" task.</li> <li><strong>The "Happy Path" of an Issue:</strong> <ol> <li>A new issue appears in <strong>UX Intake</strong> (Status: <code>Active</code> or <code>Needs review</code>, Unassigned).</li> <li>After triage, its status is changed to move it to <strong>UX Ready for Work</strong> (Status: <code>Needs work</code>, Unassigned).</li> <li>A team member assigns it to themselves, moving it to <strong>In Progress</strong> (Status: <code>Active</code>, Assigned).</li> <li>When work is ready for feedback, it moves to <strong>Review</strong> (Status: <code>Needs review</code>, Assigned).</li> <li>Once merged/completed, it moves to <strong>Done</strong> (Status: <code>Closed (...)</code>).</li> </ol> </li> </ul> > Related issue: [Issue #3555608](https://www.drupal.org/node/3555608) > Related issue: [Issue #3558401](https://www.drupal.org/node/3558401)