-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Workspace Feeds] [External] Create new Edit Card Limit page #44326
Comments
Later phase of implementation |
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue. |
Thanks |
Updates: |
The PR has been opened for the review 👀 |
Leaving this open to integrate the BE |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.14-6 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 2024-08-07. 🎊 For reference, here are some details about the assignees on this issue:
|
Issue is ready for payment but no BZ is assigned. @JmillsExpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@JmillsExpensify)
|
$250 summary above is correct for @DylanDylann |
Also remind me, are you paid via Upwork or New Expensify? |
This issue belongs to our project, There no need for payment |
Since UpdateExpensifyCardLimit API endpoint is ready I'm going to work on BE integration |
@VickyStash thanks, hit us up in Slack if you have any questions |
Can I close this issue or should I keep it open? |
We are still connecting it to the backend so lets keep it open but you do not have to be assigned |
The API call was implemented during the page implementation. There are some minor fixes/updates to make the card limit update work as expected in the PR related to OpenPolicyExpensifyCardsPage API call integration. I've tested how UpdateExpensifyCardLimit API call works, and the result looks as expected: So we can just wait till the mentioned PR is merged and it should work as expected. |
Perfect, thanks! |
Not overdue, we are actively working on this one |
@MariaHCD, @VickyStash, @mountiny, @DylanDylann Eep! 4 days overdue now. Issues have feelings too... |
This can be closed now I think |
Part of the Workspace feeds project.
Implement the following part of the design doc.
@koko57 @VickyStash @allgandalf @DylanDylann
Issue Owner
Current Issue Owner: @VickyStashThe text was updated successfully, but these errors were encountered: