FY26Q4 Stage Lead planning issue: Plan
Issue description
This issue outlines the themes that will be the focus of the Plan stage lead during Q4 of FY26.
Themes
Continue documentation support for Project Studio
- Short description:
- Reasoning:
- Note:
| Issue | Group(s) | Status | Effort | Priority | Details |
|---|---|---|---|---|---|
issue link with + to see description |
group |
Waiting for <...>
|
Low, Medium, High |
Low, Medium, High |
Target milestone is 17.x. Led by: Technical Writer (TW name) or Engineer
|
issue link with + to see description |
group |
Waiting for <...>
|
Low, Medium, High |
Low, Medium, High |
Target milestone is 17.x. Led by: Technical Writer (TW name) or Engineer
|
MRs:
Documentation support for issues as work items GA
- Short description:
- Reasoning:
- Note:
| Issue | Group(s) | Status | Effort | Priority | Details |
|---|---|---|---|---|---|
issue link with + to see description |
group |
Waiting for <...>
|
Low, Medium, High |
Low, Medium, High |
Target milestone is 17.x. Led by: Technical Writer (TW name) or Engineer
|
issue link with + to see description |
group |
Waiting for <...>
|
Low, Medium, High |
Low, Medium, High |
Target milestone is 17.x. Led by: Technical Writer (TW name) or Engineer
|
MRs:
- Document changes for issues as work items (gitlab-org/gitlab!214860 - merged) • Marcin Sedlak-Jakubowski • 18.7
- Docs: Restructure quick actions documentation (gitlab-org/gitlab!215427 - merged) • Marcin Sedlak-Jakubowski • 18.7
Documentation support for consolidated work items list
- Short description:
- Reasoning:
| Issue | Group(s) | Status | Effort | Priority | Details |
|---|---|---|---|---|---|
issue link with + to see description |
group |
Waiting for <...>
|
Low, Medium, High |
Low, Medium, High |
Target milestone is 17.x. Led by: Technical Writer (TW name) or Engineer
|
issue link with + to see description |
group |
Waiting for <...>
|
Low, Medium, High |
Low, Medium, High |
Target milestone is 17.x. Led by: Technical Writer (TW name) or Engineer
|
Quick wins
- Short description: Easy docs fixes and improvements across the stage docs.
- Reasoning: While it's important that big cross-stage improvements are planned and tracked, it's also important to recognize small but significant improvements.
Add glql list - replace Stage name and example query
example: https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/1398#quick-wins
Legend:
-
⏳ : Waiting for<...>.technical writer, orPM input, orEngineering input -
🚧 : In progress -
✅ : Complete -
🏋🏽 : Stretch goal (add next to any item that is aspirational this quarter)
Retrospective
After the quarter is complete, create discussion threads with the following titles. Use these discussion threads for self-reflection and to note feedback from others about how the quarter went.
## 👍 What went well?
## 👎 What didn't go as well?
## 📈 What could be improved for next time?
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
Edited by Marcin Sedlak-Jakubowski