You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Web - Room - Paid policy isn't shown as an option under “Workspace”. #28046
Sign into OldDot, create or navigate to an existing paid policy. Save the policyID.
Run the following snippet to enabled chat rooms for the policy.
const policyID = '';
API.policy_get({policyIDList: policyID}).then((response) => {
const policy = response.policies[policyID];
policy.areChatRoomsEnabled = true;
API.policy_save({policyID, value: policy});
Sign into NewDot (you'll need to sign out first because of the new reliable updates changes). FAB > New Room.
Expected Result:
Verify the paid policy shows up as an option under "Workspace"
Actual Result:
Paid policy isn't shown as an option under “Workspace”
Workaround:
Unknown
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: 1.3.73.0 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
The QAer didn't follow the steps correctly. The policyID they entered has carets around it <>. Those are placeholders and shouldn't actually appear in the policyID.
In addition, I'm noticing some other problems, fixing those in a PR
Activity
melvin-bot commentedon Sep 22, 2023
Triggered auto assignment to @bfitzexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Sep 22, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)bfitzexpensify commentedon Sep 25, 2023
Reproduced. @jasperhuangg, any insight on this one? It was discovered via #26982
bfitzexpensify commentedon Sep 28, 2023
Bump on #28046 (comment) @jasperhuangg
melvin-bot commentedon Oct 2, 2023
@bfitzexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
bfitzexpensify commentedon Oct 2, 2023
@jasperhuangg thoughts on #28046 (comment)?
4 remaining items
bfitzexpensify commentedon Oct 6, 2023
@jasperhuangg not sure if you're seeing my bumps, so assigning it to you so it appears in your K2. Looking for your thoughts on #28046 (comment)
jasperhuangg commentedon Oct 9, 2023
Ah, thanks for assigning me @bfitzexpensify. I wasn't receiving mention notifications for some reason. Taking a look.
jasperhuangg commentedon Oct 9, 2023
The QAer didn't follow the steps correctly. The policyID they entered has carets around it
<>. Those are placeholders and shouldn't actually appear in the policyID.In addition, I'm noticing some other problems, fixing those in a PR
bfitzexpensify commentedon Oct 9, 2023
Sweet, thanks man
melvin-bot commentedon Oct 17, 2023
@jasperhuangg, @bfitzexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Oct 19, 2023
@jasperhuangg, @bfitzexpensify Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Oct 23, 2023
@jasperhuangg, @bfitzexpensify 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
melvin-bot commentedon Oct 25, 2023
@jasperhuangg, @bfitzexpensify 10 days overdue. Is anyone even seeing these? Hello?
melvin-bot commentedon Oct 27, 2023
@jasperhuangg, @bfitzexpensify 12 days overdue now... This issue's end is nigh!
bfitzexpensify commentedon Oct 27, 2023
Looks like https://github.com/Expensify/Web-Expensify/pull/39143 was deployed to prod a couple of weeks ago - I can't reproduce any more, so I think we're good to close this.