[HOLD for payment 2023-06-28] [$1000] Email is missing in "Invite new members to workspace" page

[Beamanator]

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:

1. go to Settings >Workspaces > Members
   2.click on invite

Expected Result:

email showing for all members

Actual Result:

email is missing for all members

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?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: main
Reproducible in staging?: N
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
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan / @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686828770758129

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0131ca05869a50a814
• Upwork Job ID: 1670861674705686528
• Last Price Increase: 2023-06-19

[melvin-bot]

Triggered auto assignment to @tjferriss (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[Beamanator]

@tjferriss I don't know if we need an engineer on this - @fedirjh made the PR & i merged it - technically @fedirjh is a C+ but they didn't do C+ duties, they fixed the bug 😅 👍

[tjferriss]

@Beamanator thanks. It sounds like we should @fedirjh as the contributor and you're the reviewer.

As for the reporting bounty, I see the bug was first reported by @gadhiyamanan so I would assume we give them the reporting bonus over @priya-zha.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0131ca05869a50a814

[melvin-bot]

Triggered auto assignment to @sonialiap (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

[melvin-bot]

Current assignee @fedirjh is eligible for the External assigner, not assigning anyone new.

[priya-zha]

@Beamanator thanks. It sounds like we should @fedirjh as the contributor and you're the reviewer.

As for the reporting bounty, I see the bug was first reported by @gadhiyamanan so I would assume we give them the reporting bonus over @priya-zha.

@tjferriss I reported the same bug on June 12 whereas this issue was reported on June 15. Here's the slack convo: https://expensify.slack.com/archives/C049HHMV9SM/p1686588133599859

Also here in this convo

It would be great if you could look at this and let me know your thoughts on this. 😀 😀

Thanks

[gadhiyamanan]

@priya-zha you reported that bug for PR testing which was fixed and for that reporting bonus will be handled here and i reported after it merged with main

[priya-zha]

It's still reproducible, so was it really fixed? If a bug has been reported for a specific build, do we need to create the same bug report again and again if the PR merges with the main or hits the staging ? Actually, i don't have much idea on this , so if someone could clarify. I'll leave this on the team. Whatever the team decides , I'm okay with it. 😄😄😄😄

Also a related conversation here https://expensify.slack.com/archives/C049HHMV9SM/p1686659432203249?thread_ts=1686648377.836269&cid=C049HHMV9SM

[gadhiyamanan]

It's still reproducible, so was it really fixed?

I am not able to reproduce, are you?

[priya-zha]

@gadhiyamanan No not today. It was reproducible when the PR merged with the main. If it was already solved before the PR merged with the main , then why did the issue appear again? Also, I have a question, Can you please let me know if we create different bug reports for the same bug if it gets reproduced on a different build? I'm sorry I don't know much about this. Or is it like we just create a single bug report for a specific bug no matter what the build is? Here's where my doubt is. It would be great if you could answer this. 😃 😃

If we create different bug reports for the same bug which depends on the build/platform we use , then no doubt, you should be the one to be the reporter for this bug. But, according to this slack convo, I felt no multiple bug reports are created for the same issue. I don't know what's the procedure here. 😕 ❓ Confused totally.

[gadhiyamanan]

according to this slack convo, I felt no multiple bug reports are created for the same issue

the above bug which you mention is general bug which was reproducible in staging and not related to PR according to this. the bug which was reported by you is related to PR and which was solver according to this

the bug which was reported by me and created in GitHub was reported after merged with main

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.29-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [Fix] Missing Email in Workspace invite page #20823

If no regressions arise, payment will be issued on 2023-06-28. 🎊

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.

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty

[melvin-bot]

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:

• [@fedirjh] The PR that introduced the bug has been identified. Link to the PR:
• [@fedirjh] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@fedirjh] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@fedirjh] Determine if we should create a regression test for this bug.
• [@fedirjh] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@tjferriss] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[melvin-bot]

@Beamanator, @tjferriss, @fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick!

[Beamanator]

Ready for payment 👍

[melvin-bot]

@Beamanator, @tjferriss, @fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick!

[Beamanator]

Bump @tjferriss

[Beamanator]

Bump again @tjferriss :D

[tjferriss]

Sorry for the delay here. I meant to re-assign before heading out on vacation. Offers have been sent to @fedirjh and @gadhiyamanan for the reporting bonus.

[gadhiyamanan]

@tjferriss accepted, thanks!

[tjferriss]

Payments have been sent.