Skip to content

[Suggested Search v1] Remove Invoices and Trips from LHN, rename reports #61117

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

Open
luacmartins opened this issue Apr 29, 2025 · 5 comments
Open
Assignees
Labels
Reviewing Has a PR in review Weekly KSv2

Comments

@luacmartins
Copy link
Contributor

luacmartins commented Apr 29, 2025

Implement Remove Invoices and Trips from LHN, rename reports of the design doc

Issue OwnerCurrent Issue Owner: @JS00001
Copy link

melvin-bot bot commented May 5, 2025

@JS00001 Eep! 4 days overdue now. Issues have feelings too...

@JS00001
Copy link
Contributor

JS00001 commented May 5, 2025

Working on this, these changes are done, but all changes are being done as one so we dont have search w/ missing features

@melvin-bot melvin-bot bot removed the Overdue label May 5, 2025
@trjExpensify trjExpensify moved this to Second Cohort - CRITICAL in [#whatsnext] #migrate May 6, 2025
@melvin-bot melvin-bot bot added the Overdue label May 8, 2025
@JS00001
Copy link
Contributor

JS00001 commented May 8, 2025

in implementation, not overdue

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Overdue Daily KSv2 labels May 8, 2025
Copy link

melvin-bot bot commented May 23, 2025

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

Copy link

melvin-bot bot commented May 24, 2025

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reviewing Has a PR in review Weekly KSv2
Projects
Status: Second Cohort - CRITICAL
Development

No branches or pull requests

2 participants