-
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
[BE - Requires Internal Engineer] [$250] Web - Hold - Red dot is lost on held expense when approve pending amount #50823
Comments
Triggered auto assignment to @zanyrenney ( |
We think that this bug might be related to #wave-collect - Release 1 |
@zanyrenney FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
moving to expense. |
Job added to Upwork: https://www.upwork.com/jobs/~021846971961812039151 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ntdiary ( |
Quick question, how do we make a account approver and another employee? Thanks for any help. |
BE bug the report on hold is not returned by the BE after paying. |
@ntdiary, @zanyrenney Eep! 4 days overdue now. Issues have feelings too... |
![]() App/src/components/ReportActionItem/ReportPreview.tsx Lines 156 to 162 in 4f0ca94
When Approver goes back to room, the hold violation data doesn't exist yet, so |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@ntdiary, @zanyrenney Eep! 4 days overdue now. Issues have feelings too... |
This issue requires an internal engineer. When an employee puts an expense on hold, our app doesn't push the hold violation data to the approver, so their |
We require an internal engineer here. I have applied the lable |
@ntdiary, @zanyrenney 12 days overdue now... This issue's end is nigh! |
Eh, @zanyrenney, it seems that an internal engineer hasn't been assigned automatically? 😂 |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@ntdiary, @zanyrenney Eep! 4 days overdue now. Issues have feelings too... |
|
Seeing as we have said expense is lower priority, I am going to move this to weekly. It is tagged correctly in expense. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
1 similar comment
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
This is on Hold right now and not a priority. |
I actually think this fits in a cohort room since it definitely affects our current cohort. I've moved to #convert since we're pitching Hold to new users. |
This issue has not been updated in over 15 days. @ntdiary, @zanyrenney 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! |
@ntdiary, @zanyrenney, this Monthly task hasn't been acted upon in 6 weeks; closing. If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: v9.0.48-2
Reproducible in staging?: Y
Reproducible in production?: Y
Issue was found when executing this PR: #49910
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
Red dot should remain on held report when Approver go back to room
Actual Result:
Red dot disappears from held expense when approve pending amount. It appears only when open the held report again and navigate back to room
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6634951_1728975645603.Recording__4253.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ntdiaryThe text was updated successfully, but these errors were encountered: