-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[HOLD for payment 2024-08-02] [Workspace Feeds] [External] Create new Edit Limit Type page #44328
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
Comments
Later phase of implementation |
@VickyStash will work on this one |
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue. |
Assigned you! :) |
@MariaHCD @mountiny I have a couple of questions here:
Note: I guess the button in the screen should say 'Save' instead of the 'Next' |
For 1 & 2:
I think we might need some additional thought around how to implement this. Left some initial thoughts here but I will start a fresh discussion in the channel.
Ah, good point. I would imagine there is no point in the SmartLimit option if approvals are not configured. |
@MariaHCD does it mean it's possible this screen will have only one option - |
Yes, that's a possibility! |
@MariaHCD @mountiny Maybe I can open a PR without specific checks for now, and then we can specify them when linking the page with the backend? |
@VickyStash Yes, that sounds good to me. I'm aiming to start a discussion in the channel today. |
Hey @dubielzyk-expensify, I guess you were working on these mockups. Could you please confirm the buttons text I guess it should be cc @shawnborton |
That makes sense to me. When you are just editing a single push-row and you are not in "step-by-step flow mode", we use "Save" as the button text. And your suggestion to use "Change limit type" makes sense too. But let's definitely get a check from @dubielzyk-expensify too before moving forward. |
Yep agree that those labels make more sense 👍 |
Thanks for raising these questions! I agree with the latest copy changes, makes sense! |
The PR has been opened for the review 👀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.12-0 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-02. 🎊 For reference, here are some details about the assignees on this issue:
|
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@MariaHCD, @VickyStash, @mountiny Eep! 4 days overdue now. Issues have feelings too... |
Not overdue, the backend has been merged |
I have created a fresh issue for this one as I forgot we still had this one open. Nevertheless, I put all the details of the api command into the new issue #46959 and I think its fine to close this one and handle the integration over there @waterim @VickyStash |
Part of the Workspace feeds project.
Implement the following part of the design doc.
@koko57 @VickyStash @allgandalf @DylanDylann
The text was updated successfully, but these errors were encountered: