Skip to content

NSQS Frontend components: NSQS setup (OAuth Flow) #55496

Closed

Description

@yuwenmemon

This all will be implemented behind the nsqs beta.


Tracking Issue: https://github.com/Expensify/Expensify/issues/446352

Design Doc Section: https://docs.google.com/document/d/18g8cUtqiSwJce2a42d7uU1dLmxz6hjfVf1bIXwyz4PY/edit?tab=t.0#heading=h.jjgspdksgmgz


NSQS setup (OAuth Flow)

This is going to be a straightforward basic page NSQSSetupPage that renders a form using FormProvider.

Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @s77rt

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    NewFeatureSomething to build that is a new item.
    on Jan 21, 2025
  2. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 21, 2025
  3. melvin-bot commented on Jan 21, 2025

    @melvin-bot

    Current assignee @s77rt is eligible for the External assigner, not assigning anyone new.

  4. melvin-bot commented on Jan 21, 2025

    @melvin-bot

    Triggered auto assignment to @stephanieelliott (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.

  5. melvin-bot commented on Jan 21, 2025

    @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 ⚠️

  6. melvin-bot commented on Jan 21, 2025

    @melvin-bot

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

  7. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 21, 2025
  8. melvin-bot commented on Feb 21, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @yuwenmemon, @s77rt, @ikevin127 eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  9. s77rt commented on Feb 21, 2025

    @s77rt
    Member

    @yuwenmemon Can we close this?

  10. s77rt commented on Feb 21, 2025

    @s77rt
    Member

    or I think @ikevin127 requires payment here?

  11. yuwenmemon commented on Feb 21, 2025

    @yuwenmemon
    ContributorAuthor

    I believe payment for @ikevin127 is being handled in a different issue: #55495 (comment)

    So this should be good to close!

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

Metadata

Metadata

Labels

ExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2NewFeatureSomething to build that is a new item.ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions