>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3535026. --> Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>To better see what has already been worked on recently that aligns with the AI initiative roadmap, we want to go through issues that were worked on in June and July and update them based on:</p> <p><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai_initiative/issues/3532764" title="Status: Closed (fixed)">#3532764: Issue workflow for AI development</a></span></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Focus on new features and important enhancements rather than general bug fixing</li> <li>Make a list of projects to target beyond the AI module and Experience Builder projects, if any</li> <li>Search the issue queues for these projects for recently-updated AI-related issues</li> <li>For those that align with roadmap items or are key feature improvements, add the issue tags and info (see below)</li> <li>When updating the issue, point to this issue in the comment (see below)</li> </ul> <p><strong>USE EXISTING TAGS IF AT ALL POSSIBLE...</strong></p> <p><strong>If the tag doesn't already exist, DM Kristen in Slack to figure out the best one to use, and we'll add it to the docs.</strong></p> <p><strong>Tags:</strong></p> <ul> <li>Initiative: AI Initiative</li> <li>Month for target completion: e.g. June, July, August</li> <li>Skill focus: concept, UX, design, frontend, backend, devops [if others that aren't listed are good to use, you can use them and then add a comment on this issue with the tags) [NOTE: for closed, it's not required to add these skill tags]</li> <li>Escalation: if the issue is blocked, add the "blocker" tag and if it needs review for the product managers, add "Needs product manager review"</li> </ul> <p><strong>Additional issue triage:</strong></p> <ul> <li>Review the issue priority... it should be major if it was an important focus for the initiative and normal otherwise</li> <li>Check the status and category are correct</li> <li>Make sure the component is correct (note we now have components for all submodules)... if you aren't sure, change to "...to be triaged"</li> <li>Ideally, ensure the issue title has some context of what component it's related to, e.g. "AI Core: do the thing" or "Update AI Logging to do the thing"</li> </ul> <p><strong>Projects to include</strong></p> <ul> <li>AI module</li> <li>AI Agents module</li> <li><del>Experience Builder</del> (for now, these issues are pulled in via the "AI" component)</li> </ul> <p><strong>Comment to add:</strong></p> <pre>Updating issue metadata and tags based on [#3535026]</pre><p><br></p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Create high-level roadmap per <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai_initiative/issues/3535016" title="Status: Closed (fixed)">#3535016: Create high-level AI initiative roadmap</a></span></li> <li>Fill in the list above with any additional AI projects</li> <li>Find help to update the issues</li> <li>Try a couple/few issues and review with Kristen and refine the process if necessary</li> <li>Finish the issue updates</li> <li>Ping Jamie to try out in his new dashboard</li> </ul> > Related issue: [Issue #3532764](https://www.drupal.org/node/3532764)