[SIDEPANE] Build "Stage 3)" of "Add live-navigating help side pane"

[blazejkustra]

The design doc for Add live-navigating help side pane.

Specific help content for different types of reports

This update adds contextual help for special reports like #admins rooms and expense reports by replacing generic report IDs with meaningful labels (e.g., /r/:reportID → /r/admins). The report type will be determined using Onyx data.

cc @brunovjk @francoisl

Issue Owner

Current Issue Owner: @kadiealexander

[brunovjk]

Please assign me here as C+ since we are working on stages 1 and 2. Thanks. 🚀

[francoisl]

FYI I'm going to be on vacation for about a week starting tomorrow, so we might want to assign to another internal engineer if you have PRs to review.

[melvin-bot]

Triggered auto assignment to @kadiealexander (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[melvin-bot]

⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (NewFeature)

[quinthar]

Doing more testing over the weekend, ETA on Monday.

[quinthar]

Stage 3 is on Staging!

[dubielzyk-expensify]

Is this ready for a design review?

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.18-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Side Pane Stage 3: Specific help content for different types of reports #58847

If no regressions arise, payment will be issued on 2025-04-02. 🎊

For reference, here are some details about the assignees on this issue:

• @blazejkustra does not require payment (Contractor)
• @brunovjk requires payment (Needs manual offer from BZ)

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.26-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Reuse linkingConfig and make individual sections collapsable  #59844

If no regressions arise, payment will be issued on 2025-04-18. 🎊

For reference, here are some details about the assignees on this issue:

• @blazejkustra does not require payment (Contractor)
• @brunovjk requires payment (Needs manual offer from BZ)

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@brunovjk] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@kadiealexander] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[ikevin127]

*[x] [@ikevin127 ] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.

🟢 No regression test needed yet as the feature is behind beta flag, assuming regression tests will be added upon project completion. @kadiealexander This is for the second PR production deploy I reviewed as C+ here, for which payment is due on 2025-04-16.

[brunovjk]

As discussed on NewDot chat with Matt and Francois, and based on my Help Panel contributions, I’d like to propose the following:

• 3 larger PRs
  #56490, #58004, #58847 → $250 each ($750 total)

• 4 PRs fixing bugs and following with the implementation
  #58092, #58280, #58576, #59221 → $250 each ($1,000 total)

• 4 minor bug fixes
  #58000, #58104, #58474, #59058 → $250 total

Total: $2,000

Important: One of the issues from the bug list has already been paid by @JmillsExpensify here, so we should deduct $250 from the total.

Total: $1,750

These PRs are related to stages 1, 2, and 3 of the Help Panel implementation. The regression period for the last PR in this group ends on April 14th.

cc: @mallenexpensify @francoisl

[brunovjk]

Moving on to stage 4, we have already implemented two PRs:

• #59740 — reviewed by @ikevin127, regression period ends on April 16th
• #59844 — reviewed by me, regression period ends on April 18th

I believe we should create an issue to track the next PRs in this stage.

[brunovjk]

Summary of upcoming paydays:

• April 14th – $1,750 to @brunovjk (as detailed above)
• April 16th – $250 to @ikevin127 (please confirm the amount)
• April 18th – $250 to @brunovjk (please confirm the amount)

[mallenexpensify]

Thanks @brunovjk, looks great to me, thanks for the breakdown. @francoisl , since you're more-closely related, can you provide a comment with a 👍 to confirm then I'll get paid? Thx

[francoisl]

👍 looks correct to me

[mallenexpensify]

https://www.upwork.com/jobs/~021912146737656100430
@brunovjk can you please accept the job and reply here once you have?

[brunovjk]

@mallenexpensify Offer accepted ;)

[mallenexpensify]

Contributor+: @brunovjk paid $1,750 via Upwork.

Thanks!

Leaving open for other payments listed above for Bruno and Kevin.

[kadiealexander]

@mallenexpensify should I swap with you for this one since you've taken care of it so far? Otherwise happy to help handle the following 2 payments.

[kadiealexander]

Payment summary, all paid through Upwork:

• - April 14th – $1,750 to @brunovjk (offer)
• - April 16th – $250 to @ikevin127 (offer)
• - April 18th – $250 to @brunovjk (offer)
• - May 6th – $250 to @brunovjk - (offer)

[mallenexpensify]

@kadiealexander , please handle the upcoming payments, thx

[brunovjk]

@kadiealexander can we proceed with payment here. Later I believe we can close this issue. Thank you.

[blazejkustra]

There is one last follow up, PR is ready for review @brunovjk

[blazejkustra]

We can create a new issue for it if it makes the payment process easier.

[mallenexpensify]

We can create a new issue for it if it makes the payment process easier.

Nah, shouldn't be needed. Just post once the last PR's been on production for a week, then we can pay, thx

[brunovjk]

Payment Summary:

• April 18th – $250 to @brunovjk - For this PR
• May 6th – $250 to @brunovjk - For this PR

Note: I don't believe we need regression tests here, if I'm wrong, please tell me so I can create them right away :D

[kadiealexander]

Payment summary here. Have sent offer for the last payment.

[brunovjk]

Thank you @kadiealexander. Offer accepted

[mallenexpensify]

@brunovjk paid ya the final $250 and checked the box above.
We good to close this?

[brunovjk]

Greta!! Exactly, we can close it :D Thanks @mallenexpensify