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

Profile/Settings enhancements for portability and organization #7268

Closed
ZeroCoolGOS opened this issue Aug 13, 2020 · 3 comments
Closed

Profile/Settings enhancements for portability and organization #7268

ZeroCoolGOS opened this issue Aug 13, 2020 · 3 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

@ZeroCoolGOS
Copy link

Description of the new feature/enhancement

  1. Portable or Cloud Profiles: Have the ability to store/use our profiles remotely, such as attached to our Microsoft accounts (for example). This would allow us to set our settings once and have them accessible on any machine access. Copy and Paste the settings.json to a OneDrive account does not lend well to sync and simplicity.

  2. Multiple Profile Support: Creation for a "Work" profile, "Home" profile, "Dev" profile and "Prod" profile. (names are just examples of multiple profiles). And have them accessible at the same time if desired. Allowing for nesting or grouping of profiles.

Proposed technical implementation details (optional)

@ZeroCoolGOS ZeroCoolGOS added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 13, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 13, 2020
@skyline75489
Copy link
Collaborator

I think #2933 and #4566 are related issues.

@zadjii-msft
Copy link
Member

Yea I think @skyline75489 is right. You might also be interested in

/dup #2933
/dup #4566
/dup #1571
/dup #641
/dup #2303

@ghost
Copy link

ghost commented Aug 13, 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 Aug 13, 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 Aug 13, 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

3 participants