-
Notifications
You must be signed in to change notification settings - Fork 3k
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-10-09] [HOLD for payment 2023-10-05] Members - Clicking on 'Invite' button navigates back to Workspace page #28130
Comments
Please re-state the problem that we are trying to solve in this issue.Wrong navigation on click of 'Invite' button What is the root cause of that problem?We are navigating to workspace initial page instead of invite page What changes do you think we should make in order to solve the problem?Change route from WORKSPACE_INITIAL to WORKSPACE_INVITE to below code App/src/pages/workspace/WorkspaceMembersPage.js Lines 137 to 140 in f068ef1
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @cristipaval ( |
Seems a regression from this PR where by mistake |
Thanks! I've opened a PR to fix this. |
just opened one as well @tgolen , hahah |
I just tested on staging and it looks like this is resolved. Removing deployblocker label. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.74-3 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-10-05. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.75-12 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-10-09. 🎊 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:
|
Triggered auto assignment to @CortneyOfstad ( |
@CortneyOfstad I believe this is waiting on @thesahindia getting paid for a C+ review on the PR. Could you please facilitate that? |
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue. cc @thienlnam |
Current assignee @thesahindia is eligible for the External assigner, not assigning anyone new. |
I am also not paid for reporting bonus |
So to confirm — @Natnael-Guchima is paid $50 for reporting bonus Thanks and once I have this confirmed, I'll manually create the job in Upwork and send out the proposal contracts 👍 |
I was assigned as the C+ but I didn't do any work. The checklist was filled by @cristipaval. |
@CortneyOfstad, I wasn't paid and I am not eligible for any payment here. |
Okay, so to confirm @tgolen — does only @Natnael-Guchima get paid for the reporting bonus? |
That looks correct, yes. |
@Natnael-Guchima Sent you a proposal in Upwork. Let me know once you accept and we can get this paid — thanks! |
Accepted the offer. Thanks @CortneyOfstad |
Payment completed! Thanks all — closing! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
User should navigate to the 'Invite members' page
Actual Result:
User is navigated back to workspace page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.74.0
Reproducible in staging?: y
Reproducible in production?: n
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
Screen.Recording.2023-09-25.at.10.35.34.AM.mov
Recording.4748.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695627542846449
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: