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
[HOLD for payment 2024-12-25] [$250] iOS/Android WS features -Feature is not enabled after enabling it and upgrading workspace to Control #53360
Version Number: 9.0.69-1 Reproducible in staging?: Y Reproducible in production?: N If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y Email or phone of affected tester (no customers):applausetester+232803@applause.expensifail.com Issue reported by: Applause Internal Team
Action Performed:
Launch hybrid or ND app.
Create a Collect workspace.
Go to More features.
Enable Rules.
Tap Upgrade.
Tap Got it, thanks.
Expected Result:
Rules feature will be enabled after enabling it and upgrading workspace to Control plan (production behavior).
Actual Result:
Rules feature is not enabled after enabling it and upgrading workspace to Control plan. User has to enable it again.
👋 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:
Identify the pull request that introduced this issue and revert it.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
1. Create a Collect workspace
2. Go to More features
3. Enable Rules
4. Tap Upgrade
5. Tap Got it, thanks
6. Verify that the Rules feature is enabled
Activity
melvin-bot commentedon Dec 1, 2024
Triggered auto assignment to @muttmuure (
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.github-actions commentedon Dec 1, 2024
👋 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:
melvin-bot commentedon Dec 1, 2024
Triggered auto assignment to @carlosmiceli (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 1, 2024
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Dec 1, 2024
Job added to Upwork: https://www.upwork.com/jobs/~021863284829899625527
53 remaining items
melvin-bot commentedon Jan 3, 2025
@Ollyws, @kirillzyusko, @mountiny, @CyberAndrii, @muttmuure 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
Ollyws commentedon Jan 5, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] 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: Migrate E/App to use
PlatformStackNavigation#49937 (comment)[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
melvin-bot commentedon Jan 7, 2025
@Ollyws, @kirillzyusko, @mountiny, @CyberAndrii, @muttmuure 12 days overdue. Walking. Toward. The. Light...
mountiny commentedon Jan 7, 2025
I am not sure if we need a specific test for this one
muttmuure commentedon Jan 7, 2025
@Ollyws $250 C+
@kirillzyusko does not require payment
@CyberAndrii $250 Contributor
muttmuure commentedon Jan 7, 2025
Andrii is paid, waiting for Olly to submit request
Ollyws commentedon Jan 7, 2025
Requested on ND.
garrettmknight commentedon Jan 7, 2025
$250 approved for @Ollyws
melvin-bot commentedon Jan 13, 2025
@Ollyws, @kirillzyusko, @mountiny, @CyberAndrii, @muttmuure Huh... This is 4 days overdue. Who can take care of this?
mountiny commentedon Jan 13, 2025
I believe we can close now, thanks!