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

[HOLD for payment 2023-12-26] [$500] [Custom Status] Add the ability to automatically clear Custom User Status #23138

Closed
stitesExpensify opened this issue Jul 18, 2023 · 51 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors Waiting for copy User facing verbiage needs polishing Weekly KSv2

Comments

@stitesExpensify
Copy link
Contributor

stitesExpensify commented Jul 18, 2023

Part of the Custom Status project

Main issue: #16350
Doc: https://docs.google.com/document/d/1uPS24aoRWE45piaTvr0XvrgV1lK3lSjieG3sD5ZPfQg/edit#bookmark=id.dm0yu67h9vq8
Project: https://github.com/orgs/Expensify/projects/59/views/1

Add the ability to automatically clear Custom User Status

This will involve many new pages to set relative times, time, and date.

  1. Add "Clear After" button to the status page. This will also show the clear after time after one has been set.
    <img width="219" alt="2023-07-18_16-09-48" src="https://github.com/Expensify/App/assets/42391420/bf69bee6-dc40-4dac-be2c-b6af1b
2023-07-18_16-11-31 0f24f3">
  1. The "Clear After" page. This will expand when the user selects "custom" as you can see in the second screenshot
2023-07-18_16-10-30 2023-07-18_16-11-09
  1. The Date picker page
2023-07-18_16-11-15
  1. The Time picker page
2023-07-18_16-11-22
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01b67967a538696fdd
  • Upwork Job ID: 1724123658546638848
  • Last Price Increase: 2023-11-13
@stitesExpensify
Copy link
Contributor Author

No update here, but work has started on the base PR!

@melvin-bot melvin-bot bot removed the Overdue label Jul 28, 2023
@melvin-bot melvin-bot bot added the Overdue label Aug 7, 2023
@stitesExpensify
Copy link
Contributor Author

Base PR is in review!

@melvin-bot melvin-bot bot removed the Overdue label Aug 8, 2023
@perunt perunt mentioned this issue Aug 16, 2023
58 tasks
@melvin-bot melvin-bot bot added the Overdue label Aug 21, 2023
@stitesExpensify
Copy link
Contributor Author

Almost here!

@melvin-bot melvin-bot bot removed the Overdue label Aug 23, 2023
perunt added a commit to margelo/expensify-app-fork that referenced this issue Aug 23, 2023
perunt added a commit to margelo/expensify-app-fork that referenced this issue Aug 24, 2023
@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Weekly KSv2 labels Aug 24, 2023
perunt added a commit to margelo/expensify-app-fork that referenced this issue Aug 25, 2023
perunt added a commit to margelo/expensify-app-fork that referenced this issue Aug 28, 2023
perunt added a commit to margelo/expensify-app-fork that referenced this issue Aug 30, 2023
perunt added a commit to margelo/expensify-app-fork that referenced this issue Aug 31, 2023
@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Aug 31, 2023
perunt added a commit to margelo/expensify-app-fork that referenced this issue Sep 1, 2023
perunt added a commit to margelo/expensify-app-fork that referenced this issue Sep 4, 2023
@melvin-bot melvin-bot bot added Monthly KSv2 and removed Weekly KSv2 labels Sep 25, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 25, 2023

This issue has not been updated in over 15 days. @stitesExpensify eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

@stitesExpensify
Copy link
Contributor Author

This has been on hold with @perunt being pulled to some other projects

perunt added a commit to margelo/expensify-app-fork that referenced this issue Dec 5, 2023
Copy link

melvin-bot bot commented Dec 5, 2023

@conorpendergrast, @jamesdeanexpensify, @allroundexperts, @stitesExpensify Still overdue 6 days?! Let's take care of this!

perunt added a commit to margelo/expensify-app-fork that referenced this issue Dec 6, 2023
@stitesExpensify
Copy link
Contributor Author

Doing the final review now!

perunt added a commit to margelo/expensify-app-fork that referenced this issue Dec 13, 2023
Copy link

melvin-bot bot commented Dec 14, 2023

@conorpendergrast, @jamesdeanexpensify, @allroundexperts, @stitesExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

@stitesExpensify
Copy link
Contributor Author

This has been merged!

Copy link

melvin-bot bot commented Dec 14, 2023

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@iwiznia
Copy link
Contributor

iwiznia commented Dec 14, 2023

Context https://expensify.slack.com/archives/C01GTK53T8Q/p1702577037928319
I closed this issue #33093 since it should not block, but we should add a better error message there

Copy link

melvin-bot bot commented Dec 15, 2023

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@conorpendergrast
Copy link
Contributor

@stitesExpensify @jamesdeanexpensify Do we have an external resource update for this change? We will need to update this help page

@jamesdeanexpensify
Copy link
Contributor

I am unaware of one, maybe @stitesExpensify knows. Who usually handles that? I can make a PR if needed.

@stitesExpensify
Copy link
Contributor Author

External resource update is here https://github.com/Expensify/Expensify/issues/296265 we closed it after the previous release because we were unsure how long this would take. I'll re-open it so that the help page can be updated

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 labels Dec 19, 2023
@melvin-bot melvin-bot bot changed the title [$500] [Custom Status] Add the ability to automatically clear Custom User Status [HOLD for payment 2023-12-26] [$500] [Custom Status] Add the ability to automatically clear Custom User Status Dec 19, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Dec 19, 2023
Copy link

melvin-bot bot commented Dec 19, 2023

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

Copy link

melvin-bot bot commented Dec 19, 2023

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

If no regressions arise, payment will be issued on 2023-12-26. 🎊

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

For reference, here are some details about the assignees on this issue:

Copy link

melvin-bot bot commented Dec 19, 2023

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:

  • [@allroundexperts] The PR that introduced the bug has been identified. Link to the PR:
  • [@allroundexperts] 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:
  • [@allroundexperts] 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:
  • [@allroundexperts] Determine if we should create a regression test for this bug.
  • [@allroundexperts] 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.
  • [@conorpendergrast] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@jjcoffee
Copy link
Contributor

Just noting that I also reviewed the PR for this. Also, the base price should be $1000 as the issue was created before the change (not to mention the PR was massive 😅).

@allroundexperts
Copy link
Contributor

Can we have a payment summary here? Thanks!

@conorpendergrast
Copy link
Contributor

conorpendergrast commented Dec 20, 2023

Yep, I can write that up! I'll check some details via an internal Slack channel then come back

@conorpendergrast
Copy link
Contributor

conorpendergrast commented Dec 22, 2023

Payouts due:

Contributor: $1000 @perunt (Contractor)

After an internal discussion, we're arriving at $1000 as a balance between the scale of the work involved, and the two regressions.

Upwork job is here.

@jjcoffee
Copy link
Contributor

@conorpendergrast Accepted, thanks!

@conorpendergrast
Copy link
Contributor

@jjcoffee paid!

This was a new feature so doesn't require the checklist, so I'm closing it out. Thanks!

@JmillsExpensify
Copy link

$1,000 payment to @allroundexperts based on summary above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors Waiting for copy User facing verbiage needs polishing Weekly KSv2
Projects
None yet
Development

No branches or pull requests

8 participants