Skip to content

[Tracking] [External] Attendee Tracking project #44725

Closed

Description

@Julesssss

Important Links

Strategy

In order to jump start viral growth, we need to migrate all existing customers to NewDot as soon as possible, so they can reap the rewards of the new app we've been building for several years.

Problem

It's common that one employee incurs an expense that includes others (eg: one person buys lunch for their whole office). There's no way to clearly outline this in NewDot though, so it can easily look like they overspent. This can drive manual back and forth between employee and admin, and cause significant loss of efficiency when compounded across the organization. A less efficient experience adds friction to enticing members to make the switch to NewDot and will slow down reunification.

Solution

Add support for attendee tracking in NewDot. This will make it easy for members to clearly indicate when spend is shared with others, and should reduce back and forth about larger than normal requests. The exact scope is TBD, but my thinking is we can do this by:

  • Adding an Attendees row on requests in NewDot.
  • Allowing members tap on the row, see a list of all eligible attendees, and select from the list.
  • Surfacing selected attendees, and amount per person on request detailed.

Screenshot 2024-07-18 at 14 49 04

Implementation Issues

Frontend:

Backend

TODO

Finish the project

Post-launch polish:

Tasks

  • Post Proposal (full Problem/Solution statement) in #expensify-open-source
  • Wait at least one full business day, and until the post has a majority (2/3) of positive reactions (👍)
  • Paste Proposal in the space above with a link to the Slack thread
  • Email strategy@expensify.com and paste in the Proposal
  • Fill out the High-level overview of the problem, Timeline, and Terminology sections of the Design Doc
  • Email strategy@expensify.com (continue the same email chain as before) with the link to your Design Doc
  • Host a pre-design meeting (example) in #expensify-open-source to discuss any necessary details in public before filling out the High-level of proposed solution section.
  • Fill out the High-level of proposed solution section
  • Email stategy@expensify.com again with links to the doc and pre-design conversation in Slack
  • Add the DesignDocReview label to get the High-level of proposed solution section reviewed
  • Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary
  • Confirm that the doc has the minimum necessary number of reviews before proceeding
  • Host another pre-design meeting in #expensify-open-source to ask for engineering feedback on the technical solution.
  • Fill out the Detailed implementation of the solution and related sections.
  • Re-add the DesignDocReview label to this issue
  • Respond to any questions or concerns and bring up blockers in Slack to get consensus if necessary
  • Confirm that the doc has the minimum necessary number of reviews before proceeding
  • Email strategy@expensify.com one last time to let them know the Design Doc is moving into the implementation phase
  • Implement the changes
  • Add regression tests so that QA can test your feature with every deploy (instructions)
  • Send out a follow up email to strategy@expensify.com once everything has been implemented and do a Project Wrap-Up retrospective that provides:
    • Summary of what we accomplished with this project
    • What went well?
    • What could we have done better?
    • What did we learn?
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. deleted a comment from melvin-bot on Jul 2, 2024
  2. deleted a comment from melvin-bot on Jul 2, 2024
  3. deleted a comment from melvin-bot on Jul 2, 2024
  4. Julesssss commented on Jul 2, 2024

    @Julesssss
    ContributorAuthor

    After discussion here, I want to make the document changes much clearer before seeking help from SWM.

  5. 149 remaining items

  6. JmillsExpensify commented on May 28, 2025

    @JmillsExpensify
    Contributor

    Who's handling the regression steps for this project?

  7. francoisl commented on May 28, 2025

    @francoisl
    Contributor

    @JmillsExpensify I have a WIP issue here, but holding until we finish making Attendee Tracking a feature, so we can also add tests for that.

  8. JmillsExpensify commented on May 30, 2025

    @JmillsExpensify
    Contributor

    @mananjadhav is going to confirm that #61484 is deployed to production, though ahead of that confirmation, here's the payment summary: $500 to @mananjadhav for PR review and testing.

  9. mananjadhav commented on May 30, 2025

    @mananjadhav
    Collaborator

    @JmillsExpensify Based on my findings both the PRs are deployed to production. For #61484, we can the commits in the production branch.

    shouldDisplayTransactionAmount && ((hasReceipt && !isReceiptBeingScanned && didReceiptScanSucceed) || !isPerDiemRequest)

    (iouType === CONST.IOU.TYPE.SUBMIT || iouType === CONST.IOU.TYPE.CREATE) && !!policy?.id && (policy?.type === CONST.POLICY.TYPE.CORPORATE || policy?.type === CONST.POLICY.TYPE.TEAM)

    @Julesssss @francoisl can you also confirm? so that @JmillsExpensify can update the payment summary?

  10. francoisl commented on May 31, 2025

    @francoisl
    Contributor

    Yes, that looks correct to me.

  11. JmillsExpensify commented on Jun 9, 2025

    @JmillsExpensify
    Contributor

    Payment summary: $500 to @mananjadhav for PR review and testing.

  12. garrettmknight commented on Jun 13, 2025

    @garrettmknight
    Contributor

    $500 approved for @mananjadhav

  13. JmillsExpensify commented on Jun 25, 2025

    @JmillsExpensify
    Contributor

    I think we're done here though please re-open if something is missed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionNewFeatureSomething to build that is a new item.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions