>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3583362. --> Reported by: [afoster](https://www.drupal.org/user/594458) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>Blocked &mdash; document how to create DrupalForge-testable issues spanning multiple dev module versions<br> <strong>Check-in Date: </strong>04/13/2026<br> <strong>Additional Collaborators: </strong><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>Many AI issues span multiple modules at once. For example, when we work on UI improvements in the AI module and need to use those same improvements in CCC, reviewers need dev versions of both modules installed together to test the change. </p> <p>Setting that up locally is a barrier for UX reviewers. We need a short, repeatable guide for creating issues that come with a working DrupalForge instance running the right combination of dev branches so reviewers can click a link and leave feedback without local setup.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Write a brief doc covering: how to declare the module set and dev branches for an issue, how to spin up a DrupalForge instance with those branches installed together, how to attach the link to the issue, a paste-in template for issue authors, and basic</p> <h3 id="summary-proposed-resolution">Status</h3> <p>Blocked until feature is ready. </p>