-
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
[$250] Imported reports become "Hmm... it's not here" in new dot #46576
Comments
Triggered auto assignment to @kevinksullivan ( |
@kevinksullivan Huh... This is 4 days overdue. Who can take care of this? |
@kevinksullivan 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@kevinksullivan 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
Job added to Upwork: https://www.upwork.com/jobs/~01cad85d32f0e40e56 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @hoangzinh ( |
I think this is a low priority Control item, because it's covering a backwards compatibility edge case |
📣 @sandeepvasudewan! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Hi @sandeepvasudewan can you update your proposal with the PROPOSAL_TEMPLATE here? |
ProposalPlease re-state the problem that we are trying to solve in this issue. The problem we are addressing is that when reports are imported from the old dot to the new dot, they initially appear in the workspace chat. However, when users click on these reports, they encounter an error message: "Hmm... it's not here," rendering the reports inaccessible. What is the root cause of that problem? The root cause of the problem likely stems from discrepancies between the report identifiers, URLs, or metadata used in the old dot versus those expected in the new dot. This mismatch causes the new dot system to fail in correctly locating or displaying the imported reports, leading to the error message. What changes do you think we should make in order to solve the problem? To solve this issue, we should implement the following changes:
What alternative solutions did you explore? (Optional) Alternative solutions considered include:
|
@sandeepvasudewan you don't need to delete and then create a new comment/proposal. Just update the existing one and leave a comment update (Ref: https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md#propose-a-solution-for-the-job) Btw,
Can you give describe exactly what are differents between the report identifiers, URLs, or metadata used in the old dot versus those expected in the new dot?
Then, can you reference to which line of code in New Dot that locates imported reports as you mentioned above? Thank you |
@hoangzinh @kevinksullivan 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! |
Still waiting proposals |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Same as above |
@hoangzinh, @kevinksullivan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Still waiting proposals |
@hoangzinh, @zanyrenney Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
same as above |
@hoangzinh, @zanyrenney Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
still waiting for internal |
@zanyrenney if this issue is not a high priority, can we put it weekly? |
@hoangzinh, @zanyrenney Whoops! This issue is 2 days overdue. Let's get this updated quick! |
same as above. |
@hoangzinh, @zanyrenney Eep! 4 days overdue now. Issues have feelings too... |
@zanyrenney do you have any update from the internal team? |
@hoangzinh, @zanyrenney Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Awaiting @zanyrenney here #46576 (comment) |
hey @hoangzinh thanks for the ping. |
Seems like noone internal has been able to pick this up. Can we confirm the behaviour is still reproducible on the latest build? |
If so, I can re-flag this in the #expense room |
yes, I can still reproduce this bug |
@hoangzinh, @zanyrenney Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Waiting @zanyrenney grab an internal engineer for us |
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.14-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @hannojg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1722248571855789
Action Performed:
Expected Result:
Imported reports are usable in new dot
Actual Result:
Clicking on a report in new dot gets you the "Hmm... it's not here" error
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Screen.Recording.2024-07-29.at.12.19.55.mov
View all open jobs on GitHub
Recording.397.mp4
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @hoangzinhThe text was updated successfully, but these errors were encountered: