-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] [HOLD for payment 2024-06-11] [Wave Collect] [Xero] [Imported Features and Taxes] Make Categories, Tags, and Taxes read-only when the user is connected to Xero #39911
Comments
Triggered auto assignment to @joekaufmanexpensify ( |
Current assignee @joekaufmanexpensify is eligible for the NewFeature assigner, not assigning anyone new. |
@lakchote should I be finding someone from SWM to do this, or just waiting for someone who already committed to do it to pick it up? |
Hey! I’m Jakub Szymczak from Software Mansion, an expert agency, and I’d like to work on this issue! |
Great. TY! @SzymczakJ is there an eta for a PR here? |
@joekaufmanexpensify there should be the same task for QBO integration that would solve this issue(they also connect to accounting software and should make categories etc. read-only), but I cannot find it, so I'm not sure if it's already worked on by them. Also if nobody is taking care of it I do it 😃 cc @mountiny |
@SzymczakJ, are you referring to this issue? If so, do you mean that the QBO issue will solve this for Xero too, and we can consolidate both into that issue? |
Sorry for late response, I was OOO. The issue you mentioned isn't solving this issue completely, it only disables switches for taxes/categories but the user is still able to edit categories etc.(as shown on video). swtichblocked.movPreviously I thought that making categories/taxes read-only was also the case for QBO and that's why I said it will be solved with QBO but maybe that isn't the case. Anyways the issue you mention isn't solving our issue completely and I don't see any open QBO issue that would solve this, so I could take care of that. cc @lakchote Also is it only a Xero thing that the categories should be read-only and in case of QBO the user should be able to edit it freely? |
It shouldn't be a Xero thing only; from my understanding when you have an accounting integration connected it is the source of truth and the categories should come from this source only. So, it should be read only for both QBO and Xero from my understanding. Could we have your opinions @trjExpensify @zanyrenney please? |
Another question for design/product: How read-only state should be displayed? I have some idea but I want to make sure. readwriteflow.movWe have few options of editing: My idea would look like this: Screen.Recording.2024-05-06.at.15.45.39.movWDYT @zanyrenney @trjExpensify |
another question: the user has ability to enable/disable import of taxes,categories, etc.. We should only make taxes(and similarly categories, etc.) read-only when the import taxes toggle is on, right? |
Hey - catching up here after being OoO yesterday. To be sure I'm following the question, we're trying to decide what you shouldn't be able to do with imported coding values (i.e categories, tags, tax rates etc) when connected to an accounting solution. Is that right? If so, then the answer is you shouldn't be able to |
I've looked into this and found couple things that didn't get solved.
Also I have one important question. Should taxes, etc. be read-only when we are connected to accounting integration(with or without clicking import) or when we are connected to accounting integration AND clicking on import taxes, etc. I ask because sometimes we base on |
Did you test on dev/main, yeah? If so, @hayata-suenaga what did your PR for #41274 implement?
Can you rephrase the question, I'm not sure I'm following you. |
All good, thanks! Assigning @hungvu193 to review. |
PRs are merged but not yet deployed |
PR on staging |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.78-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-06-11. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
We already have a centralized testing script for this project, so IDT we need an ad-hoc regression test here. |
@SzymczakJ is with SWM, so only payment needed here is $250 to @hungvu193 for C+ review via Upwork. |
Job added to Upwork: https://www.upwork.com/jobs/~01bf513d396cfd4d35 |
Current assignee @hungvu193 is eligible for the External assigner, not assigning anyone new. |
Hey @joekaufmanexpensify , I got paid already so no payment needed here 😄 |
Ah, okay, sounds good! Just withdrew the upwork offer and closed the upwork job. |
In that case, we should be all set here then. Thanks everyone! |
As noted here for QBO, we need to prevent the user from taking actions when the user is connected to Xero.
When the user connects to Xero:
This will be worked on by SWM engineers, see Slack discussion here.
Until the Xero authorization flow (NewDot issue) is done (which entails NewDot, Web-E and IS changes), we won't be able to work on this yet.
Issue Owner
Current Issue Owner: @Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: