Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add openning tabs with Admin Rights from dropdown menu #6534

Closed
VidathD opened this issue Jun 16, 2020 · 2 comments
Closed

Add openning tabs with Admin Rights from dropdown menu #6534

VidathD opened this issue Jun 16, 2020 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@VidathD
Copy link

VidathD commented Jun 16, 2020

Make it so that we can open a terminal tab with admin privileges from the dropdown menu.

When you open the drop-down menu,

  1. You get a drop-down list where it is alternating as normal and admin. It would be great if you can make it so we can enable/disable this in settings as some may find this interfering. For example

Windows Power Shell
Administrator: Windows Power Shell

  1. When you click on a selection of the drop-down menu holding, for example, Shift a terminal with admin privileges open.
@VidathD VidathD added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 16, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 16, 2020
@zadjii-msft
Copy link
Member

To support this, we'd need to first support opening new instances elevated 😉. A bunch of this work is being tracked in #5000, #1032, #1490, #632. I bet once #632 and #1571 are both implemented, you could manually add entries to the new tab dropdown for { "action":"openTab", "elevated":true } or something similar (depending on how #632 shakes out).

For now, I'm gonna close this as a combo dupe of those two. Thanks!

/dup #632 #1571

@ghost
Copy link

ghost commented Jun 16, 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 ghost closed this as completed Jun 16, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 16, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants