-
Notifications
You must be signed in to change notification settings - Fork 3k
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-05-29] [HOLD for payment 2023-05-25] Prevent creating new requests from within a settled expense report #19028
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01be7b10bebf499be1 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @rushatgabhane ( |
Holding on #18604 |
Nice, I agree you shouldn't be able to @thienlnam, should you be able to |
Actually, you should be able to assign tasks anywhere - I'm not sure if it works out of the box right now because that hasn't been our focus for V1 - but technically yes should be possible! |
Yeah, is that going to break though? In which case, do we want to not show the |
It actually does work out of the box - there is a bug with the avatar in the LHN but we can fix that along with the the avatars for requests |
Cool. I think avatars for requests is being fixed if you look at the latest we're working on from here: https://expensify.slack.com/archives/C03TQ48KC/p1684276084051879?thread_ts=1684266162.911009&cid=C03TQ48KC |
No longer on hold |
Taking this over also updated the solution with more cases we will block |
Current assignee @trjExpensify is eligible for the NewFeature assigner, not assigning anyone new. |
PR merged, @rushatgabhane $1000 flat rate for the PR help |
dropping a note for Tom to hire account "Satish Gabhane" - https://www.upwork.com/freelancers/~01212e8255b02ae924 context - https://expensify.slack.com/archives/C02NK2DQWUX/p1683614947522329 |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.15-12 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-05-25. 🎊 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.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.16-7 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-05-29. 🎊 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.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Errr.. why are there two payment dates on this issue? 😕 |
I've seen this on quite a few issues over the last 2 weeks. |
So are we waiting on the 29th or is this due today? |
In the meantime, offer sent to Satish on this job in prep @rushatgabhane 👍 |
PR hit prod 7 days ago. Paid and closing. |
Yeah, the date was over a week ago. |
@trjExpensify @JmillsExpensify @luacmartins @mountiny
Problem
Currently, the requester can continue to create requests from within a settled expense report. This is not possible for the payee after refreshing the page.
Expected
Current
Solution
Blocks users from:
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: