-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[HOLD for payment 2024-05-09] [$250] Pronouns - Default Priority Mode Not Highlighted and marked, Causing Inconsistency #40789
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
Comments
Triggered auto assignment to @puneetlath ( |
@puneetlath I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
ProposalPlease re-state the problem that we are trying to solve in this issue.Pronouns - Default Priority Mode Not Highlighted and marked, Causing Inconsistency What is the root cause of that problem?The main problem with issue is that we don't set priorityMode by default when we first open the app What changes do you think we should make in order to solve the problem?We can set initialValue for priorityMode when we get this value from Onyx
App/src/pages/settings/Preferences/PriorityModePage.tsx Lines 77 to 79 in 944751f
What alternative solutions did you explore? (Optional)As alternative we can update this line like on PriorityModePage for SelectionList
Or set priorityMode by default here
Also we can start implementing
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Pronouns - Default Priority Mode Not Highlighted and marked, Causing Inconsistency What is the root cause of that problem?When
What changes do you think we should make in order to solve the problem?We need to add fallback value, just like we do in
What alternative solutions did you explore? (Optional) |
Job added to Upwork: https://www.upwork.com/jobs/~014e981393fc9a3ead |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
Wouldn't it be more efficient for the backend to simply return the |
We don't store anything if the priority mode isn't gsd, so I think it's easier to have the front-end handle the default in this scenario. |
I think @ZhenjaHorbach Proposal looks good to me. 🎀 👀 🎀 C+ reviewed |
Current assignee @puneetlath is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
Great, assigned @ZhenjaHorbach. |
📣 @fedirjh 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @ZhenjaHorbach 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR will be ready within a few days |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.69-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-05-09. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@ZhenjaHorbach has been paid. @fedirjh bump on the checklist. |
BugZero Checklist:
Regression Test Proposal
|
Issue for regression tests: https://github.com/Expensify/Expensify/issues/395853 Everyone has been paid. Thanks y'all! |
Uh oh!
There was an error while loading. Please reload this page.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.64-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The "Most Recent" default selection should be automatically highlighted and marked, aligning with other default sections like Language and Timezone
Actual Result:
The default priority mode is not highlighted or marked, causing inconsistency with other sections like Language and Timezone
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6458088_1713825671119.Screen_Recording_2024-04-22_at_3.08.28_PM.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @puneetlathThe text was updated successfully, but these errors were encountered: