[HOLD for payment 2024-05-10] [Wave Collect] [Xero] Build the Authorization flow

[lakchote]

You need to build the Xero authorization flow, following the steps outlined here.

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

Triggered auto assignment to @johncschuster (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

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

[johncschuster]

@lakchote I'm not familiar with whether or not this can be built by an external contributor. Can you help me understand to whom I should triage this?

[melvin-bot]

@johncschuster Whoops! This issue is 2 days overdue. Let's get this updated quick!

[SzymczakJ]

Hey! I’m Jakub Szymczak from Software Mansion, an expert agency, and I’d like to work on this issue!

[johncschuster]

@lakchote bump! Can I assign this one out to @SzymczakJ?

[lakchote]

@lakchote bump! Can I assign this one out to @SzymczakJ?

Sorry I've just seen your message! Yes, this can be built by an external contributor, you can assign the issue to @SzymczakJ.

Here is the Slack discussion for context, thank you!

Also @SzymczakJ, please be aware of #39955

[lakchote]

Assigned @SzymczakJ now @johncschuster as this PR is a critical one, since it's a requirement of the follow-up PRs for the different flows (Import, Export, Advanced). If we can gain time in making progress here, it'll be greatly beneficial for having momentum.

Thank you for choosing to work on this.

[johncschuster]

Bumping for Melvin. Looks like this one is being worked on above.

[mountiny]

PR merged

[lakchote]

It has been deployed to staging and production, closing the issue.

[lakchote]

It has been deployed to staging and production, closing the issue.

I realised my mistake after, and asked for confirmation with my mentor. Reopening the issue, that overdue label messed with me!

Payment date should be next Friday

cc @johncschuster

[melvin-bot]

@mananjadhav, @johncschuster, @lakchote, @mountiny, @SzymczakJ Whoops! This issue is 2 days overdue. Let's get this updated quick!

[mananjadhav]

@johncschuster This is ready for payout for C+ review.

[mountiny]

This was a large PR and @mananjadhav helped to get this done urgently, I think we should pay them $500 for their thorough review @johncschuster

[mananjadhav]

Thanks @mountiny. Appreciate it. Quick question, this was deployed on production on May 01. Shouldn't it be ready for payout by now?

[mananjadhav]

Looks like we are at May 10 anyway. @johncschuster quick bump.

[melvin-bot]

Payment Summary

Upwork Job

• Reviewer: @mananjadhav owed $500 via NewDot (price increased based on this comment)
• Contributor: @SzymczakJ is from an agency-contributor and not due payment

BugZero Checklist (@johncschuster)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[johncschuster]

Payment summary has been updated (Thanks for the incredible work, @mananjadhav and @SzymczakJ!). Please request $500 in NewDot, @mananjadhav!

[JmillsExpensify]

$500 approved for @mananjadhav