-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[$250] New draft reports and additional expenses added to a draft report will not mark a workspace chat unread #49184
Comments
Job added to Upwork: https://www.upwork.com/jobs/~021834641825011202120 |
Triggered auto assignment to @VictoriaExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 ( |
@garrettmknight Can you upload a vid? It isn't clear. I see it gets unread for the first expense the submitter creates but for the second expense of course it doesn't get unread as for the second expense a report action will only be created for the iou report; not to the workspace chat because until the report is submitted the expenses will be inserted in to the same expense report. |
@garrettmknight @FitseTLT can you confirm if as per the business the expense on draft report should be in read state? |
i'll try to reproduce this today |
I would think this probably also needs a back-end update. That we'll need to update how this works optimistically, but also from the back-end. |
@puneetlath I need an answer here as it can potentially be a dupe. |
Looks very similar to #37315, @puneetlath @garrettmknight Is it possible to get the videos/screenshot for this |
I think it's a bit different: |
Just confirmed that additional expenses don't mark unread, it's just new draft reports. Updating OP. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
We are looking for proposals : |
The expected result is illogical our current behaviour is the correct one because users should be informed, by marking the workspace chat unread, that there is a new draft report. |
@FitseTLT I think the issue is that the Workspace chat should be shown as Unread when there is new information/messages the user is not aware of. As the creator of the expense, the submitter's workspace chat does not need to be marked as unread because there is nothing they need to be notified of. @garrettmknight please correct me if I have that wrong |
Not overdue |
not overdue, awaiting proposals |
@VictoriaExpensify It is confusing. From the OP, it seems the expected result is from the approver's side and what I am opposing is making the workspace chat as read from the approver's side. But if the OP is for the submitter's side it is the current behaviour of the app as it will open the workspace chat when you submit the expense it is not unread. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@VictoriaExpensify @ishpaul777 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@VictoriaExpensify, @ishpaul777 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
We are waiting for proposals |
@VictoriaExpensify, @ishpaul777 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@VictoriaExpensify, @ishpaul777 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
We dont have any proposals melvin, we are waiting for proposals |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
bumped in slack |
Hi, I'm Julian from Callstack - expert agency - and I would like to work on this issue. |
@VictoriaExpensify, @ishpaul777 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@jasperhuangg I think this issue will get swallowed up by the proposed changes to the unread summary handling and what not. Do you want to take this over? close it and handle it elsewhere? or provide more direction on what we want to do in this issue, so it's not conflicting the plan? |
not overdue, Callstack member will look into this one and we are also pulling Jasper for some direction on this issue |
The reason this happens is because even though there is a draft "comment" (expense) in the report, the |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
I think we probably just shouldn't tackle this right now since it seems like whatever we do here could wind up getting undone by the expense submission notification improvements project. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: N/A
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @coleaeason
Slack conversation: https://expensify.slack.com/archives/C06ML6X0W9L/p1725978630280069?thread_ts=1725864497.268339&cid=C06ML6X0W9L
Action Performed:
Expected Result:
The Submitter's workspace chat is not unread when they create a new draft report.
Actual Result:
The submitter's workspace chat is marked unread when they create a new draft report.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
All
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ishpaul777The text was updated successfully, but these errors were encountered: