[GH-ISSUE #1153] Edit User Usage Location Populate #628

Closed
opened 2026-03-02 12:43:50 +03:00 by kerem · 4 comments
Owner

Originally created by @schneiderbw on GitHub (Oct 11, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1153

Description

When editing an existing user, the Usage Location is populated in the Raw User Data section, but not in the Account Details section of the edit user screen. Could we prefill the Usage Location with the current user information?

Screenshot: https://i.imgur.com/m5JQU92.png

Environment data

Azure

Frontend: 2.14.0 (Latest)
Backend: 2.3.1 (Latest)
Originally created by @schneiderbw on GitHub (Oct 11, 2022). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1153 ### Description When editing an existing user, the Usage Location is populated in the Raw User Data section, but not in the Account Details section of the edit user screen. Could we prefill the Usage Location with the current user information? Screenshot: https://i.imgur.com/m5JQU92.png ### Environment data ```PowerShell Azure Frontend: 2.14.0 (Latest) Backend: 2.3.1 (Latest) ```
kerem 2026-03-02 12:43:50 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 11, 2022):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:1275009931 --> @github-actions[bot] commented on GitHub (Oct 11, 2022): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@KelvinTegelaar commented on GitHub (Oct 11, 2022):

This is because your usage location in Avatar -> Profile is set to blank, either set it to the preferred location or anything not blank.

<!-- gh-comment-id:1275011146 --> @KelvinTegelaar commented on GitHub (Oct 11, 2022): This is because your usage location in Avatar -> Profile is set to blank, either set it to the preferred location or anything not blank.
Author
Owner

@schneiderbw commented on GitHub (Oct 11, 2022):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

<!-- gh-comment-id:1275011311 --> @schneiderbw commented on GitHub (Oct 11, 2022): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
Author
Owner

@dsghi commented on GitHub (Oct 26, 2022):

@KelvinTegelaar, this should be classified as a bug; the usage location should be populated from the user account, not the logged-in user, as user accounts can vary per tenant, and we're not always managing a tenant that is in our geographic location.

<!-- gh-comment-id:1292733736 --> @dsghi commented on GitHub (Oct 26, 2022): @KelvinTegelaar, this should be classified as a bug; the usage location should be populated from the user account, not the logged-in user, as user accounts can vary per tenant, and we're not always managing a tenant that is in our geographic location.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#628
No description provided.