AI Workflow

Overview

This workflow covers all tickets related to AI features released to our customer base.

Workflow

During this phase of the process, the scope of Support will be to gather all relevant feedback regarding bugs and feature enhancements. After gathering the necessary information, such as errors, outcomes and expected outcomes, support should add this information to the feedback issue specific to the AI feature.

AI Features table

This table links to the epic name or production documentation, along with the relevant feedback issue to use.

AI Feature	Feedback issue
AI for Developer Teams: Suggested Reviewers	Issue
AI for Developer Teams: Code suggestions	Issue
AI for Developer Teams: Summarize my MR review	Issue
AI for Developer Teams: Summarize proposed MR Changes	Issue
AI for Security and Operations: Explain this vulnerability	Issue
AI for Security and Operations: Explain this block of code in repository UI	Issue
AI for Security and Operations: Generate tests in MR	Issue
AI for Everyone: Summarize Issue Comments	Issue
AI for Everyone: GitLab Chat	Issue
AI for Everyone: Fill in merge request descriptions with AI	Issue

How to check if a customer has valid GitLab Duo Pro seats

Purchased duo pro seats are added as add-ons in a customer’s main subscription that has either Premium or Ultimate seats.

For both Self-Managed and GitLab.com, impersonating the customer’s account is the most straightforward method for checking if a subscription has Duo Pro seats:

1. Locate the customer’s CustomersDot account by searching using the customer’s email domain in https://customers.gitlab.com/admin/customer.

2. Impersonate the CustomersDot account that has a Subscription label and check the details for Duo Pro seats

   • NOTE: Always check the start and end date of the Duo Pro add-on seats

Other optional methods are below:

• For Self-Managed, follow the below steps until Duo Pro seat count is displayed in Licenses page is implemented:
  1. Locate the customer’s CustomersDot account by searching using the customer’s email domain in https://customers.gitlab.com/admin/license.
  2. Click on the i icon to navigate to the license details page.
  3. Scroll down and copy the License Key.
  4. Navigate to the Validate License page.
  5. Paste the license key in the License File box and click on Validate.
  6. Find the code_suggestions_seat_count value that is under the restrictions key. A non-zero value means that the customer should have Duo Pro seats available.
  7. Alternatively, you can request the customer to verify by checking GitLab Duo Pro page in their instance.
• For GitLab.com, follow the below steps until Duo Pro seat count is displayed in Orders page and Display if a user has Duo Pro seat assigned in Admin page are implemented:
  • If you have GitLab.com Admin access, verify the GitLab group has Duo Pro by checking the Usage Quotas page

How to check if a customer has a valid GitLab Duo Pro trial

When a customer follows these steps to start a GitLab Duo Pro trial, they get a 60 day trial for a maximum of 50 seats by default.

Self-Managed Duo Pro trials

1. Navigate to the Self-Managed Duo Pro trials page in CustomersDot.
2. Search using the customer’s email domain, company name or subscription.
3. Alternatively, you can request the customer to verify by checking GitLab Duo Pro page in their instance.
   • NOTE: Always check the start and end date of the Duo Pro trial

GitLab.com Duo Pro trials

All GitLab.com Duo Pro trials can be located using this query: https://customers.gitlab.com/admin/order?query=saas-gitlab-duo-pro-trial-plan-id

1. Navigate to the Orders page is CustomersDot.
2. Search using the customer’s Namespace ID.
3. Locate an order that has plan saas-gitlab-duo-pro-trial-plan-id.
4. If you have GitLab.com Admin access, verify the GitLab group has Duo Pro by checking the Usage Quotas page.
   • NOTE: Always check the start and end date of the Duo Pro.

Troubleshooting AI

While we have customer facing troubleshooting documentation, you can also look for more information in Kibana pubsub-mlops-inf-gprd-* index. Use one of the following keywords to search:

• json.jsonPayload.gitlab_host_name, the value for GitLab.com is gitlab.com.
• json.jsonPayload.url, https://codesuggestions.gitlab.com/ for GitLab Code Suggestion and https://cloud.gitlab.com/v1/chat/agent for GitLab Duo chat.

When troubleshooting make sure to get debug logs for the relevant extension.

Feel free to open issues for how AI team can collaborate with support team in the editor extensions Team issue tracker https://gitlab.com/gitlab-org/editor-extensions/meta/-/issues.