Closed mountiny closed 6 months ago
Triggered auto assignment to @puneetlath (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Platforms
in OP are ✅)Current assignee @puneetlath is eligible for the NewFeature assigner, not assigning anyone new.
I would like to do this
@chiragsalian I don't think you need me here so going to un-assign. But feel free to re-assign me if I missed something.
@chiragsalian could you apply the Review
label to this doc?
:wave: Hello Generalist Track Team - you have been assigned to review this High Level Design Doc. Please, treat this as a priority. Review this Stack Overflow for some tips on reviewing a design doc. Once you are done, simply press the Add "Reviewed Doc" comment
button in the right hand side K2 pannel or follow these instructions.
@jasperhuangg
(Expensifier / Graduate) - https://github.com/Expensify/App/issues/21006@sarajojacobson
(Expensifier / Graduate) - https://github.com/Expensify/App/issues/21007@zsgreenwald
(Project Manager) - https://github.com/Expensify/App/issues/21008@StefStavri
(Project Manager) - https://github.com/Expensify/App/issues/21009@laurenreidexpensify
(Product Manager) - https://github.com/Expensify/App/issues/21010@robertjchen
(Product Manager) - https://github.com/Expensify/App/issues/21011@cead22
(Generalist) - https://github.com/Expensify/App/issues/21012@anmurali
(Generalist) - https://github.com/Expensify/App/issues/21013@HaleyJacobson
(Accounting Technical Team) - https://github.com/Expensify/App/issues/21014Design doc link here.
I have read and reviewed this Design Doc.
Coming from this slack post, please prioritize reviewing the design doc as a daily effort if you are not focusing on SNH since this feature is a critical feature for NewDot.
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
In progress, looks like we got most of the review comments. @robertjchen would you also be able to review the comment linking design doc soon (asking cause you are the only product manager reviewer pending before we can move to the technical section review)
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
Alright looks like we got the required number of high-level reviews. Let's move ahead to the technical review. @perunt when you get a chance remember to go over all high-level comments and address them.
:wave: Hello Generalist Track Team - you have been assigned to review this Detailed Design Doc. Please, treat this as a priority. Review this Stack Overflow for some tips on reviewing a design doc. Once you are done, simply press the Add "Reviewed Doc" comment
button in the right hand side K2 pannel or follow these instructions.
@jasperhuangg
(Expensifier / Graduate) - https://github.com/Expensify/App/issues/22568@CortneyOfstad
(Expensifier / Graduate) - https://github.com/Expensify/App/issues/22569@zsgreenwald
(Project Manager) - https://github.com/Expensify/App/issues/22570@StefStavri
(Project Manager) - https://github.com/Expensify/App/issues/22571@cead22
(Product Manager / Generalist + Engineer) - https://github.com/Expensify/App/issues/22572@robertjchen
(Product Manager / Generalist + Engineer) - https://github.com/Expensify/App/issues/22573@joelbettner
(Product Manager / Generalist + Engineer) - https://github.com/Expensify/App/issues/22574@johnmlee101
(Product Manager / Generalist + Engineer) - https://github.com/Expensify/App/issues/22575@anmurali
(Product Manager / Generalist + Non-Engineer) - https://github.com/Expensify/App/issues/22576@laurenreidexpensify
(Product Manager / Generalist + Non-Engineer) - https://github.com/Expensify/App/issues/22577@stephanieelliott
(Product Manager / Generalist + Non-Engineer) - https://github.com/Expensify/App/issues/22578@RobertLadue
(Product Manager / Generalist + Non-Engineer) - https://github.com/Expensify/App/issues/22579I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I'm going help shepherd this initiative while @chiragsalian's away.
Still need 3 non-engineering product managers / generalists to review the detailed, and 2 project managers.
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I just updated the rollout plan to include a bit more detail.
At this point, this doc has gone through many reviews and revisions, and we are only short 2 non-engineering generalists, so I'm doing a last call here. This project will go into the implementation phase tomorrow.
I have read and reviewed this Design Doc!
Going to move this forward into the implementation phase and start creating issues now.
Created a project board to start tracking implementation: https://github.com/orgs/Expensify/projects/62/views/1, also created an internal issue to make that project board publicly visible
Alright, all the issues have been created. Feel free to follow the implementation in the GitHub Project
I have read and reviewed this Design Doc!
Posted project update in slack: https://expensify.slack.com/archives/C01GTK53T8Q/p1690393798476199
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
Weekly update:
GetOlderActions
and GetNewerActions
previousReportActionID
Onyx migration PR was just mergedpreviousReportActionID
to all reportActions in Auth. It's taken longer than it should have, but should be ready for review by EODNot overdue, still in progress.
I'm curious about the progress, could we please get an update like @roryabraham's last one above? 🙏
Hey, sorry my updates here have been lackluster on this issue, but I did drop an update in slack last week here
@aldo-expensify raised his hand on https://github.com/Expensify/App/issues/23218, thanks @aldo-expensify! I'm still working on https://github.com/Expensify/Web-Expensify/pull/38662
Also, I'm making this issue a daily since we're shooting to finish this by end-of-offshore
We had a number of PRs merged for this last week. Still working on the last backend piece then this should be prettymuch all front-end.
Actively implementing :working:
previousReportActionID
isn't really working due to old reportActions being cached in PHP. Created https://github.com/Expensify/Auth/pull/8764 to fix it
@chiragsalian, @roryabraham, @perunt Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Quick EOW update:
previousReportActionID
, which will be needed for the next step which actually enables comment linkingHas been delayed by my OOO but I just commented on the PR to hopefully help unblock it
Triggered auto assignment to @cristipaval, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
Did Melvin assign me by mistake or I'm missing something
This issue has not been updated in over 15 days. @roryabraham, @perunt 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!
This is a public issue to track implementation of the Comment Linking feature (internal link).
Margelo will work on the App implementation of this project
Design doc can be found here - also internal
Roll out plan
Upwork Automation - Do Not Edit