Skip to content

[Awaiting Payment 25th June] [QBO] Implement the Required toggle in the RHP with multiLevel tags. #41374

Closed

Description

@trjExpensify

Coming from here and a follow-up to this PR.

  1. We need to implement a new command to allow making an individual tag level required (i.e Customers required, Classes not required)
  2. Add the Required toggle in the RHP of each tag level when multiTags are enabled with QBO, like so:
image

CC: @luacmartins @s77rt @hayata-suenaga @aldo-expensify @zanyrenney

Activity

  1. melvin-bot commented on May 1, 2024

    @melvin-bot

    Current assignee @trjExpensify is eligible for the NewFeature assigner, not assigning anyone new.

  2. trjExpensify commented on May 10, 2024

    @trjExpensify
    ContributorAuthor

    That PR is still in review.

  3. trjExpensify commented on May 14, 2024

    @trjExpensify
    ContributorAuthor

    That PR has merged. @hayata-suenaga this is backend right to implement that command?

  4. hayata-suenaga commented on May 14, 2024

    @hayata-suenaga
    Contributor

    @trjExpensify, yes it involves the backend change.

    Currently, we have SetPolicyRequiresTag.

    That code is just enabling all tags in the tags list if there is a tags list (I assume this means that the parent level tags or multi level tags).

    We either need to create a new Web-E command or modify the existing command to accomodate the multi level tag situation.

    I'll try to work on this but might need some help from @aldo-expensify. I'll open a draft PR today and assign @aldo-expensify so that we can work together.

  5. trjExpensify commented on May 14, 2024

    @trjExpensify
    ContributorAuthor

    Cool, I was looking at this on OldDot early to see what we call when we set one of the levels as required:

    image

    .. and equally, enable/disable one of the imported tag list's tag values:

    image

    Not sure if you looked at that, or if it's helpful here.

  6. 18 remaining items

  7. hayata-suenaga commented on Jun 19, 2024

    @hayata-suenaga
    Contributor

    Yes, Rodrigo is working on a regression fix in this PR

  8. hayata-suenaga commented on Jun 24, 2024

    @hayata-suenaga
    Contributor

    The fix for the regression was deployed to production.

    The payment is handled in this issue. Closing this issue now. Thank you everyone!

  9. trjExpensify commented on Jun 24, 2024

    @trjExpensify
    ContributorAuthor

    Alright, but doesn't that mean @s77rt is required payment of $125 for the initial PR?

  10. hayata-suenaga commented on Jun 25, 2024

    @hayata-suenaga
    Contributor

    that's right! Good thing I didn't close this issue 😓

  11. hayata-suenaga commented on Jun 25, 2024

    @hayata-suenaga
    Contributor

    @trjExpensify, if you could handle that payment, I'd appreciate it 🙇

  12. trjExpensify commented on Jun 25, 2024

    @trjExpensify
    ContributorAuthor

    Cool, @s77rt sent you an offer! Payment summary as follows:

    • $125 for the C+ review of the PR

    Thanks!

  13. changed the title [-][QBO] Implement the `Required` toggle in the RHP with multiLevel tags.[/-] [+][Awaiting Payment 25th June] [QBO] Implement the `Required` toggle in the RHP with multiLevel tags.[/+] on Jun 25, 2024
  14. s77rt commented on Jun 25, 2024

    @s77rt
    Member

    @trjExpensify Accepted! Thanks!

  15. trjExpensify commented on Jun 25, 2024

    @trjExpensify
    ContributorAuthor

    Paid!

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 productionDailyKSv2NewFeatureSomething to build that is a new item.

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions