Editor Extensions 17.8 Planning
Milestone Duration
- December 16, 2024 - January 12, 2025
Our Planning Boards
- LS + VS Code - Planning Board by Crew Member
Here - JetBrains + Visual Studio + NeoVim + Eclipse - Planning Board by Crew Member
Here
Product Themes
-
Duo foundation
- Get Visual Studio to parity with VS Code and JetBrains
- Enable cycling through code suggestions
- Enable users to add additional languages for code suggestions
- Visual Studio: Support adding project files to Duo Chat
- Get Visual Studio to parity with VS Code and JetBrains
-
Duo adoption
- Visual Studio: Display code suggestion states via icons in the gutter
-
Duo stickiness
- Add /fix to code actions in VS Code
- Enable sending terminal output to Duo in VS Code
-
Platform foundation
- Continue work on enabling SAST MVC in VS Code
-
Editor Expansion
- Continue foundational work for Eclipse, with goal of first integrating code suggestions and duo chat
Roadmap
Editor Extensions product roadmap
Capacity
- We have an estimated weight budget of .
- VS Code + LS -
weight
|slippage
- JetBrains + Visual Studio -
x
|slippage
- VS Code + LS -
- Note to Engineers:
- If you have not assigned weights to your issues, please do so by
x
- Please see the
handbook for estimate guidance.
- If you have not assigned weights to your issues, please do so by
17.8
Editor Extension Release Schedule for We have established a release cadence for the following editor extensions (starting in Milestone 17.1
)
JetBrains
- Please see
the JetBrains Release DRI docs for details on the process.
Date | Release Officer | Shadow | Status | Comments |
---|---|---|---|---|
2024-12-16 | n/a | Not released |
Ad-hoc to release [JetBrains] IDE /help command may receive no re... (gitlab-jetbrains-plugin#799 - closed) per request from @tlinz v3.5.4 |
|
2024-12-17 | Released |
v3.5.5 - release link |
||
2025-01-07 |
VS Code
- Please see
the VS Code Release DRI docs for details on the process.
Date | Release Officer | Shadow | Status | Comments |
---|---|---|---|---|
2024-12-31 | @michaelangeloio | @andrei.zubov | ||
2025-01-07 | @michaelangeloio | @andrei.zubov |
Visual Studio
- NEW: To Be Added
Date | Release Officer | Shadow | Status | Comments |
---|---|---|---|---|
@bohdanpk | @john-slaughter | |||
Eclipse
- NEW: To be added once the release DRI document is done.
Date | Release Officer | Shadow | Status | Comments |
---|---|---|---|---|
TBD | @erran | @kjamoralin | ||
Crew Ramp Up Issues
If you're new to the Editor Extensions team or expanding your expertise into a new area, please checkout our Ramp-up Issues list.

Temporary section to track the issues we'll need to roll-over from previous milestone.
Prioritized Issues
- Our PM has earmarked issues as workflowready for development
handbook - The issues which are listed below and included above in our crew planning boards are our top priorities for Milestone 17.6
- Each issue has been (or will be assigned) the Deliverable or Stretch label during this Milestone.
VS Code
JetBrains
Epic | Type | Issue | Engineering Label | Assignee | Weight | Notes |
---|---|---|---|---|---|---|
typebug | IntelliJ IDEA - Blank chat window after clickin... (gitlab-jetbrains-plugin#790 - closed) | Deliverable | @aspringfield | customer reported | ||
[JetBrains] Integrate Duo Chat WebView from Lan... (&135) | typemaintenance | [JetBrains] Integrate Duo Chat WebView from Lan... (&135) | @lauraionel | DA: Is there anything we can start on in the epic or do we need to wait until the language server work is done | ||
Integrate Duo Chat WebView from Language Server (gitlab-org&15661) | typemaintenance | [JetBrains] Migrate Duo Components on the Jetbr... (gitlab-jetbrains-plugin#798 - closed) | Deliverable | @kjamoralin | Part of the migration, looks like this part can be done independently |
Visual Studio
Epic | Type | Issue | Engineering Label | Assignee | Weight | Notes |
---|---|---|---|---|---|---|
[Visual Studio] Implement adding context items ... (&119) | typefeature | @bohdanpk | May not need a lot of work on this as the LS integration may take care of the majority of the effort. | |||
Visual Studio Extension Parity (&105) | typemaintenance | [Visual Studio] Build pipelines: Improve tracki... (gitlab-visual-studio-extension#82 - closed) | Deliverable | @bohdanpk | ||
Visual Studio Extension Parity (&105) | typefeature | [Visual Studio] Show Duo icon for Code Suggestions (gitlab-visual-studio-extension#171 - closed) | Deliverable | @bohdanpk | ||
Visual Studio Extension Parity (&105) | typefeature | [Visual Studio] Enable adding additional languages (gitlab-visual-studio-extension#168 - closed) | Deliverable | @bohdanpk |
Eclipse
Language Server
Next Up
---
display: table
fields: labels("Editor Extensions::*"),labels("type::*"),title, assignees, state, closed
---
group="gitlab-org" and label="group::editor extensions" and label= "Next Up"
Checklist
-
Refine the issues already assigned to the current milestone for correct label hygiene
- Add vision items
- Product to mark issues as workflowplanning breakdown before the 4th of the month
- Product to add themes & outcomes to the planning issue
- EM to identify the available capacity for the milestone
- PM to add workflowready for development issues
- EM to add Deliverable or Stretch to the issues
- Refine the issues already assigned to the current milestone for correct label hygiene
- Check/update past milestones for wayward issues
- Add security items
- Add bugs
- Carefully check planning priority items for customers are scheduled or well communicated
Stable Counterparts
- Technical Writing ( @aqualls)