Consider adding connection grouping lists #8727

Closed
opened 2026-01-31 01:36:34 +00:00 by claunia · 2 comments
Owner

Originally created by @GentelmanBastard on GitHub (Jun 1, 2020).

Hey,

I am loving the Windows Terminal however with multiple connection profiles, the list quickly gets unreadable. Is there a plan to implement connection grouping like a list of ssh connections to dev environments and other list of qa environments and another list for production environment. It would also be nice to have ability to import such connection tree from .xml file like putty generates.

Best regards.

Originally created by @GentelmanBastard on GitHub (Jun 1, 2020). Hey, I am loving the Windows Terminal however with multiple connection profiles, the list quickly gets unreadable. Is there a plan to implement connection grouping like a list of ssh connections to dev environments and other list of qa environments and another list for production environment. It would also be nice to have ability to import such connection tree from .xml file like putty generates. Best regards.
claunia added the Resolution-Duplicate label 2026-01-31 01:36:34 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jun 1, 2020):

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #1571 for more discussion.

/dup #1571 #6083

I'd also check out #5888, which has got a spec in progress for this feature 😄

@zadjii-msft commented on GitHub (Jun 1, 2020): Thanks for the suggestion! Please make sure to [search for duplicates](https://github.com/microsoft/terminal/issues?q=is%3Aissue+group+is%3Aclosed) when filing new issues. This is already being tracked by another issue on our repo - please refer to #1571 for more discussion. /dup #1571 #6083 I'd also check out #5888, which has got a spec in progress for this feature 😄
Author
Owner

@ghost commented on GitHub (Jun 1, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 1, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8727