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.

Sign up for GitHub

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

Jump to bottom

Bug Report: Program shortcuts do not expose "Run as a different user" #1642

Closed
PGomersall opened this issue Jun 26, 2019 · 1 comment
Closed

Bug Report: Program shortcuts do not expose "Run as a different user" #1642

PGomersall opened this issue Jun 26, 2019 · 1 comment
Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@PGomersall
Copy link

Program shortcuts do not expose "Run as a different user" only "Run as administrator" on shift right-click.

Environment

Windows 1903 18362.175 Education x64
Windows Terminal version (if applicable): 0.2.1715.0

Expected behavior

"Run as a different user" is available on shift right-click

Actual behavior

Only "Run as administrator" is available
@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 26, 2019
@PGomersall PGomersall changed the title Bug Report Bug Report: Program shortcuts do not expose "Run as a different user" Jun 26, 2019
@DHowett-MSFT
Copy link
Contributor

This isn't possible with store-deployed applications, so I'm duping it to #1386

@DHowett-MSFT DHowett-MSFT added Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. Area-Build Issues pertaining to the build system, CI, infrastructure, meta and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 26, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Resolution-Answered Related to questions that have been answered Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DHowett-MSFT @PGomersall