FY26Q2 Stage Lead planning issue: AI-powered
Issue description
This issue outlines the themes that will be the focus of the AI-powered stage lead during Q2 of FY26.
Themes
Write tutorials for Duo
- Short description: Write tutorials for Duo features
- Reasoning: GitLab documentation has traditionally focused on features, and
howto use them. We have received feedback from DevRel that providing documentation that talks aboutwhyusers should use these features, with a clear narrative example, would be helpful for users and possibly increase adoption of Duo features. - Note: These issues were carried over from FY26Q1.
| Issue | Group(s) | Status | Effort | Priority | Details |
|---|---|---|---|---|---|
| +#1241 (closed) | groupai framework | Complete | High |
High |
Target milestone is 18.3. Led by: @jglassman1
|
Update documentation for granular project and group level control for Duo Core
- Short description: Update Duo documentation to account for the fact that, from 18.2 (July 17th 2025), Premium & Ultimate customers will have better user access controls as they will be able to determine which groups & projects get access to Duo Core.
- Reasoning: To ensure the documentation reflects the latest product reality
- Note:
| Issue | Group(s) | Status | Effort | Priority | Details |
|---|---|---|---|---|---|
| +https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1363 | groupai framework | Ongoing | High |
High |
Target milestone is 18.2. Led by: @jglassman1
|
Update documentation for some Duo Enterprise features to become Duo Pro features
- Short description: Update Duo documentation to account for the fact that, from 18.2 (July 17th 2025), some Duo Enterprise-only features will become Duo Pro and Enterprise features.
- Reasoning: To ensure the documentation reflects the latest product reality
- Note: N/A
| Issue | Group(s) | Status | Effort | Priority | Details |
|---|---|---|---|---|---|
|
https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1365 +https://gitlab.com/gitlab-org/gitlab/-/issues/538409 |
groupai framework | Ongoing | High |
High |
Target milestone is TBC - implementation delayed. Led by: @jglassman1 |
Identify and fill gaps in feature doc coverage
- Make sure documentation covers all necessary features and information
- Reasoning: The AI-powered space moves very quickly, and some information can be missed.
- Note: These issues were carried over from FY26Q1
| Issue | Group(s) | Status | Effort | Priority | Details |
|---|---|---|---|---|---|
| +#1236 | Multiple | Ongoing | High |
High |
Target milestone is 18.3. Led by: @jglassman1
|
| +#1235 (closed) | Multiple | Ongoing | High |
High |
Target milestone is 18.3. Led by: @jglassman1
|
| +#1238 | Multiple | Ongoing | High |
High |
Target milestone is 18.3. Led by: @jglassman1
|
| +#1239 | Multiple | Ongoing | High |
High |
Target milestone is 18.3. Led by: @jglassman1
|
| +#1264 | Multiple | Ongoing | High |
High |
Target milestone is 18.3. Led by: @jglassman1
|
| +#1351 | Multiple | Ongoing | High |
High |
Target milestone is 18.3. Led by: @jglassman1
|
| Issue TBC - gitlab-org/gitlab!192265 (comment 2547085846) | Multiple | Ongoing | High |
High |
Target milestone is 18.2. Led by: @jglassman1
|
Legend:
-
⏳ : Waiting for<...>.technical writer, orPM input, orEngineering input -
🚧 : In progress -
✅ : Complete -
🏋🏽 : Stretch goal (add next to any item that is aspirational this quarter)
Ongoing tasks
Manage TW-DRI assignments for all milestones:
Specific TW milestone planning issues:
-
X.Y. Release date: YYYY-MM-DD -
X.Y. Release date: YYYY-MM-DD -
X.Y. Release date: YYYY-MM-DD
References
- Stage leads
- Previous issue:
issue link
Edited by Jon Glassman