Changing issues to work items in labs

1. Navigate to your *Duo Demo* project.

1. In your project, from the left sidebar, select **Plan > Issues**.

1. In your project, from the left sidebar, select **Plan > Work Items**.

1. Select **New item**.

1. In the **Type** field, ensure that **Issue** is selected.

1. For the Title, input `Update hello world visuals`.

1. Leave the description blank for now and create the issue by selecting **Create issue**.

## Task C. Review the state of your project issues

1. Open `Plan > Issues` using the menu on the left. You get a list with existing issues.

1. Open `Plan > Work items` using the menu on the left. You get a list with existing issues.

1. In the upper-right corner, click the **Add New Chat** icon and select the **Planner** Agent. During this workshop we will be taking advantage of our new Agentic AI features, so make sure **Agentic mode** is still selected.

To test this, let's first create a new issue in our project.

1. In the left sidebar, select **Plan > Issues**.

1. In the left sidebar, select **Plan > Work items**.

1. Select **New issue**.

1. Select **New item**.

1. Ensure that the **Type** field is set to **Issue**

1. In the issue title, input `Create compliance frameworks`.

1. Navigate back to the `GitLab Swag Shop Flows` project.

1. Navigate to **Plan > Issues**.

1. Navigate to **Plan > Work items**.

1. Click **New item**.

1. Ensure that the **Type** field is set to **Issue**.

1. Enter the following title:

   ```prompt

- Foundational flows enabled under **Settings > General > GitLab Duo features**.

- A pipeline completed successfully under **Build > Pipelines**.

- The live Swag Shop application visible at the Pages URL, with no featured products identified on the homepage.

- A newly created issue titled **Add Featured Products Styling to Homepage** under **Plan > Issues**, with the full requirements and acceptance criteria visible in the issue description.

- A newly created issue titled **Add Featured Products Styling to Homepage** under **Plan > Work items**, with the full requirements and acceptance criteria visible in the issue description.

## Task B: Use a Foundational Flow to Create a Merge Request

**Explore B: Review the CI/CD Pipeline**

The agent session runs inside a CI/CD pipeline job, providing a traceable record of all agent-driven actions.

The agent session runs inside a CI/CD pipeline job. Each CI/CD pipeline job logs all executed tasks and generated outputs, creating a complete audit trail of the build process.

1. Navigate to **Build > Pipelines** in the left sidebar.

1. Locate the pipeline tagged as an `agent session`.

1. Locate the pipeline for adding featured products styling.

   > **Note:** You will need to wait for the two edit tests to complete.

1. Click the pipeline ID to open the pipeline details page.

1. Click the pipeline ID or status to open it.

1. Review the pipeline stages displayed, such as build, test, and deploy.

1. Select **workload** to review active tasks, resource usage, and generated outputs.

1. Click on a specific job name within a stage, like build-static, to view the job details.

1. Review the job logs to see executed steps, any warnings or errors encountered, and artifacts generated and their locations.

**Explore C: Confirm Branch Creation**

With the agent session complete, review and merge the agent's changes the same way you would any other contribution. Your team's review process, CI checks, and security requirements remain the final gate before merging.

1. Navigate to **Code > Merge Requests** and open the merge request created by the agent.

1. Navigate to **Code > Merge requests** and open the merge request created by the agent.

1. Select the **Changes** tab to review all files modified or created by the agent.

1. After you confirm all pipeline stages have passed, navigate back to the **Overview** tab.

1. Scroll down and click the **Merge** button that displays after the request is ready.

1. Scroll down and click **Mark as ready**.

1. Then, select the **Merge** button that displays after the request is ready.

Merging the merge request integrates the agent's changes into the main branch.

With the changes merged, the pipeline will run and deploy the updated application to Pages.

1. Navigate to **Build > Pipelines** and wait for the Pages pipeline to complete.

1. Navigate to **Build > Pipelines**, and find the merge request.

1. Click the **status**, and wait for the pipeline to complete.

1. Return to the Swag Shop browser tab and refresh the page.

Confirm that the agent completed all expected actions by checking for the issues, merge requests, branches, and comments it created.

1. Navigate to **Plan > Issues** and confirm three issues have been created.

1. Navigate to **Plan > Work items** and confirm three issues have been created.

   > You will see a total of 4 issues in your project. One that was created in lab 1, and three created by Duo Agentic chat. 

1. Navigate to **Code > Merge Requests** and confirm three merge requests have been created, each linked to its corresponding issue.

   > To validate that a merge request is linked to an issue, in the merge request overview tab, look for the line `Closes <issue-id>`

1. Open the merge request "fix: improve text contrast on product cards for WCAG compliance" and confirm a comment has been added.

   >**Note**:  To validate that a merge request is linked to an issue, in the merge request overview tab, look for the line `Closes <issue-id>` in the **Preview** section.

1. Navigate to **Code > Branches** and confirm three new branches are visible.

### Expected Output: Task A

- Three issues are listed under **Plan > Issues**, each with a title and description.

- Three issues are listed under **Plan > Work items**, each with a title and description.

- Three merge requests are listed under **Code > Merge Requests**, each linked to its corresponding issue.

- Three branches are visible under **Code > Branches**.

- One comment is posted to the third merge request.

- A structured analysis is in the chat panel covering the project's maintainability and scalability considerations.

- A prioritized list of quick wins is available.

- A new issue is under **Plan > Issues** with a title and description derived from the analysis.

- A new issue is under **Plan > Work items** with a title and description derived from the analysis.

- The issue is assigned to yourself.

## Task C: Review Project Health with the Planner Agent

The Planner Agent combines product management expertise with knowledge of GitLab's planning features. In this task, you will use it to identify gaps in your backlog and then resolve them directly from the chat.

1. Navigate to **Plan > Issues** using the left sidebar.

1. Navigate to **Plan > Work items** using the left sidebar.

1. Click **Add New Chat** and select **Planner**. Confirm Agentic mode is on.