Skip to content

[Tracking] [Suggested Search v2.1] Suggested Search v2.1 Unapproved Accruals #64583

Closed
1 of 1 issue completed

Description

Activity

  1. 22 remaining items

  2. changed the title [-][Tracking] [Suggested Search v2.1] Suggested Search v2.1[/-] [+][Tracking] [Suggested Search v2.1] Suggested Search v2.1 Unapproved Accruals[/+] on Jul 9, 2025
  3. s77rt commented on Jul 9, 2025

    @s77rt
    Member

    Given that this is a project, I think payment is handled differently and after the project is completed. Some of the merged PRs require another "completing" PR for BE integration

  4. ikevin127 commented on Jul 9, 2025

    @ikevin127
    Contributor

    @s77rt I'd prefer to have the payments sent as we complete issues / PRs and I think it's fine this way because we're having separate PRs for each part, regardless of it being FE only (dev lock) or complete with BE integration, meaning if any PR has a regression the default bounty will be cut in that 7-day regression period.

    If you'd prefer to be paid at the end of the project, I don't have any objections - as for myself I'd prefer to have the payments sent as we complete issues / PRs after the 7-day regression period as stated.

    I don't think it will happen, but if there will be any issues with getting paid that way, I can always reimburse.

  5. JS00001 commented on Jul 23, 2025

    @JS00001
    ContributorAuthor

    Closing this specific issue out, since its no longer the parent of our new release cycle, and all child issues have been moved to new releases. New issues have been created for releases 2.1 through 2.8

  6. JmillsExpensify commented on Sep 30, 2025

    @JmillsExpensify
    Contributor

    $875 approved for @s77rt

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

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions