Improve the UX of user creation for secondary user stores from the console app

[vismayigur]

Purpose

fixes wso2/product-is#21325

Fix the users page user store selector so it preserves the currently selected user store context after the add-user flow.

Previously, when creating a user from a secondary user store context, the users page dropdown could visually fall back to the primary user store because the selector was using a static defaultValue. This PR updates the selector to use the current selectedUserStore state so the UI stays aligned with the active context.

Related Issues

• N/A

Related PRs

• N/A

Checklist

• e2e cypress tests locally verified. (for internal contributers)
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Relevant backend changes deployed and verified
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines
• Ran FindSecurityBugs plugin and verified report
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets

Developer Checklist (Mandatory)

• Complete the Developer Checklist in the related product-is issue to track any behavioral change or migration impact.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

📝 Walkthrough

Walkthrough

The userstore selector dropdown in the users list page is changed from uncontrolled (defaultValue) to controlled (value), using selectedUserStore state with a fallback to primaryUserstoreName.

Changes

Controlled userstore dropdown

Layer / File(s)	Summary
Dropdown controlled value fix features/admin.users.v1/pages/users.tsx	Replaces defaultValue with value={ selectedUserStore ?? primaryUserstoreName } on the userstore dropdown, making it reflect the current selectedUserStore state.

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error)

Check name	Status	Explanation	Resolution
Changeset Required	❌ Error	PR diff vs origin/master includes only features/admin.users.v1/pages/users.tsx; no non-README .changeset/*.md file is present.	Add a new .changeset/*.md entry for the feature change (not README), listing the affected package(s) and version bump.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title is related to the change, but it is broader than the specific selector state fix in the users page.
Description check	✅ Passed	The description follows the template and includes purpose, issue reference, checklist items, security checks, and developer checklist.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

• 🛠️ create changeset

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[pavinduLakshan]

Hi @vismayigur, could you please add a screen recording of how your fix works, to the PR description?