Room - No audit trail when removing members from a custom room (not #admin/#announce)

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 1.3.87-1

Reproducible in staging?: Yes

Reproducible in production?: No, new feature

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

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com
2. Go to a room with a few members
3. Click on the room header > Members
4. Remove a few members

Expected Result:

There will be a system message for member removal, just like the behavior in #admin room when inviting user to the workspace

Actual Result:

There is system message for member invitation but not for member removal

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Bug6242998_1697722779956.20231019_201925.mp4

MacOS: Desktop

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (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

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @Julesssss (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[Julesssss]

Reproducible in production?: No, new feature

Not a blocker if this is a new feature

[melvin-bot]

Current assignee @Christinadobrzyn is eligible for the NewFeature assigner, not assigning anyone new.

[Christinadobrzyn]

I can reproduce this and I do think this would be helpful for our audit logs. I'm going to reach out in expensify-open-source to see if we want to do this.

2023-10-19_14-44-08.mp4

[Christinadobrzyn]

https://expensify.slack.com/archives/C01GTK53T8Q/p1697748638516129

[Julesssss]

I wouldn't be surprised if this was a backend task, unfortunately. Which is a problem, because I won't be able to work on it for at least a month

[Christinadobrzyn]

yeah sounds like we've already discussed adding this (and other details) in the audit trail but have decided to table it for now. So going to close this as a feature request that we'll consider later.