SettingsUI: keep &#34;page&#34; when changing profile #13587

@vefatica commented on GitHub (Apr 23, 2021):

In my case, I wanted to compare the appearances of various profiles. Moving around among the profiles took twice the mouse clicks. Starting at "General" is arbitrary (might as well start elsewhere) and doesn't seem to serve any purpose.

@vefatica commented on GitHub (Apr 23, 2021): In my case, I wanted to compare the appearances of various profiles. Moving around among the profiles took twice the mouse clicks. Starting at "General" is arbitrary (might as well start elsewhere) and doesn't seem to serve any purpose.

claunia commented

@zadjii-msft commented on GitHub (Apr 26, 2021):

Team consensus: lets do it.

@zadjii-msft commented on GitHub (Apr 26, 2021): Team consensus: lets do it.

claunia commented

@vefatica commented on GitHub (Apr 26, 2021):

Suits me. Watch all the complaints. 😁

@vefatica commented on GitHub (Apr 26, 2021): Suits me. Watch all the complaints. 😁

claunia commented

@DHowett commented on GitHub (Apr 26, 2021):

Team consensus: lets do it.

Suits me. Watch all the complaints. 😁

Sorry? "Let's do it" is common parlance for "let us implement the thing that has been requested"...

@DHowett commented on GitHub (Apr 26, 2021): > Team consensus: lets do it. > Suits me. Watch all the complaints. 😁 Sorry? "Let's do it" is common parlance for "let us implement the thing that has been requested"...

claunia commented

@vefatica commented on GitHub (Apr 26, 2021):

I figured that. What's your point? Was I wrong to close the issue?

@vefatica commented on GitHub (Apr 26, 2021): I figured that. What's your point? Was I wrong to close the issue?

claunia commented

@DHowett commented on GitHub (Apr 26, 2021):

Yeah! We're gonna use this issue to track completing the work to make the profiles page remember where it was. Why'd you close it? 😄

@DHowett commented on GitHub (Apr 26, 2021): Yeah! We're gonna use this issue to track completing the work to make the profiles page remember where it was. Why'd you close it? :smile:

claunia commented

@vefatica commented on GitHub (Apr 26, 2021):

I figured a decision was the end. You don't always use an original suggestion to do the tracking, do you?

@vefatica commented on GitHub (Apr 26, 2021): I figured a decision was the end. You don't always use an original suggestion to do the tracking, do you?

claunia commented

@zadjii-msft commented on GitHub (Apr 26, 2021):

You don't always use an original suggestion to do the tracking, do you?

Not always, but like 99.97% of the time we do. We usually only file our own versions for follow-ups. Like, #653 is the thread tracking adding support for quake mode, but #8888 is the thread for "everything related to quake mode after the initial PR". The only exceptions I can think of are #1564 and #5000

@zadjii-msft commented on GitHub (Apr 26, 2021): > You don't always use an original suggestion to do the tracking, do you? Not always, but like 99.97% of the time we do. We usually only file our own versions for follow-ups. Like, #653 is the thread tracking adding support for quake mode, but #8888 is the thread for "everything related to quake mode after the initial PR". The only exceptions I can think of are #1564 and #5000

claunia commented

@DHowett commented on GitHub (Apr 26, 2021):

AHH! I understand. Sorry! Yeah, Mike's got it here. We love to use the original issue since it lets the suggester know how we're doing, too. 😄

@DHowett commented on GitHub (Apr 26, 2021): AHH! I understand. Sorry! Yeah, Mike's got it here. We love to use the original issue since it lets the suggester know how we're doing, too. :smile:

claunia commented

@vefatica commented on GitHub (Apr 26, 2021):

Then what ... someone comes back here, notes that it has been implemented, and closes it? I don't see a lot of that but I admit that I'm not paying close attention to many issues.

@vefatica commented on GitHub (Apr 26, 2021): Then what ... someone comes back here, notes that it has been implemented, and closes it? I don't see a lot of that but I admit that I'm not paying close attention to many issues.

claunia commented

@DHowett commented on GitHub (Apr 26, 2021):

So, we use these issues (user suggestions, user bug reports, user requests even) as the currency of work tracking in our project. We talk about them all the time -- "let's fix 376" or "9920 is a good idea, let's do it" and then use that issue mostly for the lifetime of the request.

We mention it in any pull request, too:

"Closes #XXXX" or "Fixes #XXXX" are two keywords GitHub picks up to automatically close the related bug when the pull request merges
"Related to #XXXX" adds a link between the bug and the PR so somebody who's interested in how the work is going can follow it.

Once the feature is complete and released, the commit and the changelog entry mentions the pull request number. Our release bot finds all issues "Closed" or "Fixed" by any PR mentioned in the changelog, and tells the original submitter that their submitted issue, request, etc. was addressed in whatever version mentioned it.

@DHowett commented on GitHub (Apr 26, 2021): So, we use these issues (user suggestions, user bug reports, user requests even) as the currency of work tracking in our project. We talk about them all the time -- "let's fix 376" or "9920 is a good idea, let's do it" and then use that issue _mostly_ for the lifetime of the request. We mention it in any pull request, too: * "Closes #XXXX" or "Fixes #XXXX" are two keywords GitHub picks up to automatically close the related bug when the pull request merges * "Related to #XXXX" adds a link between the bug and the PR so somebody who's interested in how the work is going can follow it. Once the feature is complete and _released_, the commit and the changelog entry mentions the pull request number. Our release bot finds all issues "Closed" or "Fixed" by any PR mentioned in the changelog, and tells the original submitter that their submitted issue, request, etc. was addressed in whatever version mentioned it.

claunia commented

@DHowett commented on GitHub (Apr 26, 2021):

I realize that I set a bad precedent with your issues specifically. I've closed them early when I did not agree with them, only to come back and fix the issue anyway. That makes it look like we track the work elsewhere . . . and I'm sorry about that! 😄

@DHowett commented on GitHub (Apr 26, 2021): I realize that I set a bad precedent with your issues specifically. I've closed them early when I did not agree with them, only to come back and fix the issue anyway. That makes it look like we track the work elsewhere . . . and I'm sorry about that! :smile:

claunia commented

@vefatica commented on GitHub (Apr 26, 2021):

OK, that sounds vaguely familiar. Thanks for the explanation.

@vefatica commented on GitHub (Apr 26, 2021): OK, that sounds vaguely familiar. Thanks for the explanation.

claunia commented