Skip to content
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

[CRITICAL] [$250] #announce room should default to 'Admins Only' for posting #42417

Closed
garrettmknight opened this issue May 21, 2024 · 53 comments
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2

Comments

@garrettmknight
Copy link
Contributor

garrettmknight commented May 21, 2024

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: v1.4.73-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): N/A
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL: N/A
Issue reported by: @garrettmknight
Slack conversation: https://expensify.slack.com/archives/C05RECHFBEW/p1715886822520169

Action Performed:

  1. Create a workspace
  2. Navigate to the #announce room for your new workspace
  3. Open the chat settings

Expected Result:

Who can post should be defaulted to Admin only as it was designed in this doc

Actual Result:

Who can post is set to All members

Workaround:

You can set it to admins only.

Platforms:

All

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01d20a5670a3bdd03e
  • Upwork Job ID: 1792954078450966528
  • Last Price Increase: 2024-08-08
  • Automatic offers:
    • nkdengineer | Contributor | 102491174
Issue OwnerCurrent Issue Owner: @danieldoglas
@garrettmknight garrettmknight added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels May 21, 2024
Copy link

melvin-bot bot commented May 21, 2024

Triggered auto assignment to @miljakljajic (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@nkdengineer
Copy link
Contributor

Proposal

Please re-state the problem that we are trying to solve in this issue.

Who can post is set to All members

What is the root cause of that problem?

When we create a new workspace, the announce room has writeCapability as undefined in optimistic data and then BE returns it as all.

undefined,

What changes do you think we should make in order to solve the problem?

We should pass writeCapability as CONST.REPORT.WRITE_CAPABILITIES.ADMINS here to fix the offline case for announce room

undefined,

And BE also need to return writeCapability of announce room as admin in CreateWorkspace API

What alternative solutions did you explore? (Optional)

NA

@garrettmknight garrettmknight added the External Added to denote the issue can be worked on by a contributor label May 21, 2024
Copy link

melvin-bot bot commented May 21, 2024

Job added to Upwork: https://www.upwork.com/jobs/~01d20a5670a3bdd03e

@melvin-bot melvin-bot bot changed the title #announce room should default to 'Admins Only' for posting [$250] #announce room should default to 'Admins Only' for posting May 21, 2024
@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label May 21, 2024
Copy link

melvin-bot bot commented May 21, 2024

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

@eVoloshchak
Copy link
Contributor

The fix is pretty straightforward, @nkdengineer's proposal looks good to me!
Changes to BE would also be needed

🎀👀🎀 C+ reviewed!

Copy link

melvin-bot bot commented May 22, 2024

Triggered auto assignment to @lakchote, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Copy link

melvin-bot bot commented May 27, 2024

@eVoloshchak, @lakchote, @miljakljajic Eep! 4 days overdue now. Issues have feelings too...

@melvin-bot melvin-bot bot added the Overdue label May 27, 2024
@lakchote
Copy link
Contributor

@nkdengineer's proposal LGTM.

I'll take care of the BE changes.

@melvin-bot melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label May 28, 2024
Copy link

melvin-bot bot commented May 28, 2024

📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

@nkdengineer
Copy link
Contributor

We have a draft PR here
@lakchote please let me know when BE is done

Copy link

melvin-bot bot commented May 31, 2024

@eVoloshchak, @lakchote, @miljakljajic, @nkdengineer Whoops! This issue is 2 days overdue. Let's get this updated quick!

@melvin-bot melvin-bot bot added the Overdue label May 31, 2024
Copy link

melvin-bot bot commented Jun 4, 2024

@eVoloshchak @lakchote @miljakljajic @nkdengineer 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!

Copy link

melvin-bot bot commented Jun 4, 2024

@eVoloshchak, @lakchote, @miljakljajic, @nkdengineer 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

@melvin-bot melvin-bot bot added the Overdue label Aug 16, 2024
@danieldoglas danieldoglas added Monthly KSv2 and removed Weekly KSv2 labels Aug 19, 2024
@melvin-bot melvin-bot bot removed the Overdue label Aug 19, 2024
@danieldoglas danieldoglas added Weekly KSv2 and removed Monthly KSv2 labels Aug 19, 2024
@danieldoglas
Copy link
Contributor

Sorry, there are some other competing priorities which are taking some time before this.

@danieldoglas
Copy link
Contributor

All backend PRs were created. We need to wait for the reviews/deploys - probably done by the end of the week

@melvin-bot melvin-bot bot added the Overdue label Aug 28, 2024
@danieldoglas
Copy link
Contributor

Last backend PR was merged, should be deployed Monday and we can close this.

@melvin-bot melvin-bot bot removed the Overdue label Aug 29, 2024
@danieldoglas
Copy link
Contributor

This is done in the backend. @nkdengineer all yours to finish the app pr

@nkdengineer
Copy link
Contributor

@danieldoglas thank you, I'm working on this PR now

@nkdengineer
Copy link
Contributor

@danieldoglas Currently, after creating a new workspace, I am unable to access the announce room.

bug-resize.mp4

@danieldoglas
Copy link
Contributor

You need your workspace with at least 4 people to have an announce room. This was changed recently.

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Weekly KSv2 labels Sep 5, 2024
@nkdengineer
Copy link
Contributor

@eVoloshchak this PR is ready for review

@garrettmknight
Copy link
Contributor Author

Merged, awaiting delpoy - should be deployed to staging today.

@miljakljajic
Copy link
Contributor

seems like this PR went out over 7 days ago, so I've paid @nkdengineer and providing a payment summary below for @eVoloshchak

@eVoloshchak is owed 250 for their work reviewing this issue.

@miljakljajic
Copy link
Contributor

If there are any further actions to take, please assign another BZ team member - I am out on extended leave from the end of the day.

@eVoloshchak
Copy link
Contributor

  • The PR that introduced the bug has been identified. Link to the PR: no PR that has caused this, this is an initial implementation on the back end
  • 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: N/A
  • 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: Not needed, it isn't a bug per se, rather a change in expected behavior
  • Determine if we should create a regression test for this bug.
    Is it easy to test for this bug? Yes
    Is the bug related to an important user flow? Yes
    Is it an impactful bug? No

    We don't need a regression test here, this will no break as long as back end fix is not reversed

@JmillsExpensify
Copy link

$250 approved for @eVoloshchak

@JmillsExpensify
Copy link

Opening back up for the regression test.

@JmillsExpensify JmillsExpensify self-assigned this Oct 2, 2024
@JmillsExpensify
Copy link

Milja is out so I'll take this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2
Projects
No open projects
Status: CRITICAL
Development

No branches or pull requests

8 participants