Skip to content

[HOLD for payment 2024-07-26] [HOLD for payment 2024-07-24] [HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [Guided Setup Stage 2] [$500] Make the GBR on tasks at highest context and assign onboarding tasks to users #41619

Closed

Description

@anmurali

We are currently deliberately not assigning the onboarding tasks to users because the GBRs on the tasks are at lowest context. I.e. each task is shown in the LHN with a GBR and it looks very noisy and potentially annoying. But we're losing out by doing this because after the first read, the user can ignore the chat with their onboarding tasks, or worse forget where it was originally and kinda lose motivation.

So, let's

  • Make the GBR on tasks at highest context
  1. if the user that the task is assigned to is in the parent chat where the task is shared, then the GBR is at that parent chat level
  2. If the user that the task is assigned to is NOT in the parent chat where the task is shared, then the GBR is at the task level
  • Assign all the onboarding tasks created for a user to said user
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01c009eba2b6e9b0b1
  • Upwork Job ID: 1787595574563139584
  • Last Price Increase: 2024-07-15
  • Automatic offers:
    • cretadn22 | Contributor | 102769474
Issue OwnerCurrent Issue Owner: @puneetlath

Activity

  1. cretadn22 commented on May 5, 2024

    @cretadn22
  2. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 6, 2024
  3. changed the title [-]Make the GBR on tasks at highest context and assign onboarding tasks to users[/-] [+][$250] Make the GBR on tasks at highest context and assign onboarding tasks to users[/+] on May 6, 2024
  4. melvin-bot commented on May 6, 2024

    @melvin-bot
  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 6, 2024
  6. added and removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on May 6, 2024
  7. melvin-bot commented on May 6, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (External)

  8. melvin-bot commented on May 6, 2024

    @melvin-bot

    Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.

  9. removed their assignment
    on May 7, 2024
  10. allroundexperts commented on May 7, 2024

    @allroundexperts
    Contributor

    Taking over!

  11. 113 remaining items

  12. changed the title [-][HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [Guided Setup Stage 2] [$500] Make the GBR on tasks at highest context and assign onboarding tasks to users[/-] [+][HOLD for payment 2024-07-24] [HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [Guided Setup Stage 2] [$500] Make the GBR on tasks at highest context and assign onboarding tasks to users[/+] on Jul 17, 2024
  13. melvin-bot commented on Jul 17, 2024

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2024-07-24. 🎊

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

  14. changed the title [-][HOLD for payment 2024-07-24] [HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [Guided Setup Stage 2] [$500] Make the GBR on tasks at highest context and assign onboarding tasks to users[/-] [+][HOLD for payment 2024-07-26] [HOLD for payment 2024-07-24] [HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] [Guided Setup Stage 2] [$500] Make the GBR on tasks at highest context and assign onboarding tasks to users[/+] on Jul 19, 2024
  15. melvin-bot commented on Jul 19, 2024

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2024-07-26. 🎊

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

  16. puneetlath commented on Jul 19, 2024

    @puneetlath
    Contributor

    Reminder for myself -- @cretadn22 is owed $500 for two PRs. And @allroundexperts is owed $750 for 3 PRs.

  17. cretadn22 commented on Jul 30, 2024

    @cretadn22
    Contributor

    @puneetlath The payment is ready

  18. puneetlath commented on Jul 30, 2024

    @puneetlath
    Contributor

    Payment summary:

    Thanks everyone!

  19. moved this from Release 2: Summer 2024 (Aug) to Done in [#whatsnext] #wave-collecton Jul 30, 2024
  20. JmillsExpensify commented on Aug 21, 2024

    @JmillsExpensify
    Contributor

    $750 approved for @allroundexperts

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 productionEngineeringExternalAdded to denote the issue can be worked on by a contributorInternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions