-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2023-09-20] [$500] MacOS: Context Menu does not translate to Spanish #25704
Comments
Triggered auto assignment to @michaelhaxhiu ( |
Bug0 Triage Checklist (Main S/O)
|
Proposal from @ygshbht ProposalPlease re-state the problem that we are trying to solve in this issue.The issue is that on the Expensify MacOS app, the What is the root cause of that problem?The current setup for the Lines 42 to 57 in 21146e5
What changes do you think we should make in order to solve the problem?To address this issue, the
Additionally, for custom menu items that we're manually appending, the label can be set directly within the
Please note this is the bulk of solution, minor modifications such as listening to language change events and recreating the menu also need to be done to ensure the app functions like in the video below |
Thanks! Solution video: context.translation.solution.mp4 |
@michaelhaxhiu Eep! 4 days overdue now. Issues have feelings too... |
EDITED: I had to brew on this one. I think it's a valid issue to fix, but it's small and non-urgent. For that reason I want to propose we dock the payments to be as follows for this one-off: Bug reporting bonus: $250 I'm stating these now before I assign the |
Job added to Upwork: https://www.upwork.com/jobs/~01780b67747fbfff83 |
Current assignee @michaelhaxhiu is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan ( |
Upwork job price has been updated to $250 |
@michaelhaxhiu At the very least, I think the bug reporting price is fixed $250 |
I got a little ahead of myself 🐴 there's a change underway, but it's not announced. I updated my prior comment. The updated amounts for the bounty are as follows: Bug reporting bonus: $250 |
Upwork job price has been updated to $500 |
@michaelhaxhiu, @situchan Eep! 4 days overdue now. Issues have feelings too... |
@michaelhaxhiu @situchan this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@situchan The PR is ready for review! If you want to add more translations to the other lables that |
I think they're out of scope. These are all app uses: |
Ok |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.68-17 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 2023-09-20. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue: As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
Bump for payment @michaelhaxhiu |
Does this not get 50% bonus? |
I am basing my price point on Vit's slack comment in #expensify-open-source here:
This was assigned Sept 5, and merged sept 11 (delay likely due to feature freeze). This scenario exact scenario is what Vit outlined in his commentimo. But at the same time... I get that there was some mixed guidance on this GH issue about bonuses and so this is totally fair for you to ask @ygshbht. If you & situ or @neil-marcellini feel strongly, I am obviously open to offering the bonus. I just was trying to fairly apply the rule in slack across the board. As you can imagine this gets hairy for a BZ to discern when we start making one-off exceptions from the rule of thumb. |
@situchan do you get paid via NewDot or Upwork? upwork Example of bonus applied: #25889 (comment) |
I approved the proposal on September 6th, the PR was raised the same day, C+ approved on the 8th, I approved and merged on the 12th. So it was good to merge within 3 days, but I was slow to review. I think we should give the bonuses @michaelhaxhiu. |
Cool thanks for input @neil-marcellini (and sorry if i was a lil strict on my initial take, yall 😓) |
All are paid. @situchan can you please complete the BZ checklist so that we can close this? |
No regression. This is for desktop only, Spanish only, context menu only which is super rare care for the user. I think this is enough reason why we don't wanna add regression test step. |
Cool, I agree that this was just a candid oversight. Closing! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
ContextMenu options are translated to Spanish like MenuItems in ToolBar
Actual Result:
ContextMenu options are not translated to Spanish
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: v1.3.55-7
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
context.translation.issue.mp4
2023-08-19.23.11.17.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ygshbht
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691379420264869
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: