Skip to content
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

[Payment Due 4 Oct] [$250] Workspace connected to integration (NetSuite) should not allow editing of GL codes on imported tags. #49179

Closed
1 of 6 tasks
m-natarajan opened this issue Sep 13, 2024 · 27 comments
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2

Comments

@m-natarajan
Copy link

m-natarajan commented Sep 13, 2024

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Version Number: 9.0.33-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @twisterdotcom
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1726160556242179

Action Performed:

  1. User have Control workspace connected to Netsuite
  2. Select the workspace from settings(Connected to Netsuite)
  3. Click Tags > Classifications > Accessories
  4. Add GL code and save
  5. Resync the connection
  6. Repeat step 3

Expected Result:

Shouldn't allow adding a GL code for imported Tags

Actual Result:

Able to add GL code for imported code

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

image

Snip - (2) New Expensify - Google Chrome

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021836971613968760708
  • Upwork Job ID: 1836971613968760708
  • Last Price Increase: 2024-09-20
  • Automatic offers:
    • c3024 | Reviewer | 104092521
Issue OwnerCurrent Issue Owner: @RachCHopkins
@m-natarajan m-natarajan added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Sep 13, 2024
Copy link

melvin-bot bot commented Sep 13, 2024

Triggered auto assignment to @RachCHopkins (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@twisterdotcom
Copy link
Contributor

I think the Expected and Actual result are incorrect here. We just shouldn't allow adding a GL code for imported Tags. We shouldn't persist them after sync.

@RachCHopkins
Copy link
Contributor

Yeah I will update that GH title, it's not quite right.

@RachCHopkins RachCHopkins changed the title Adding a GL code to a Tag synced from an integration (ie NetSuite), it doesn't persist after syncing the connection again. Workspace connected to integration (NetSuite) should not allow appending of manual Tags Sep 16, 2024
@RachCHopkins
Copy link
Contributor

RachCHopkins commented Sep 16, 2024

Expected Result:

Shouldn't allow manual adding a non-imported GL code

Actual Result:

Able to add GL code manually

@mkzie2
Copy link
Contributor

mkzie2 commented Sep 16, 2024

Edited by proposal-police: This proposal was edited at 2024-09-16 05:07:41 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

Able to add GL code for imported code

What is the root cause of that problem?

We always allow the user to edit the GL code without checking whether we've connected to an accounting or not.

<MenuItemWithTopDescription
title={currentPolicyTag['GL Code']}
description={translate(`workspace.tags.glCode`)}
onPress={navigateToEditGlCode}

What changes do you think we should make in order to solve the problem?

We should use PolicyUtils.hasAccountingConnections function to check the workspace has an accounting or not. Then we can pass interactive prop as this check here. We can also display the right icon as lock icon

const hasAccountingConnections = PolicyUtils.hasAccountingConnections(policy);
iconRight={hasAccountingConnections ? Expensicons.Lock : undefined}
interactive={!hasAccountingConnections}

<MenuItemWithTopDescription
title={currentPolicyTag['GL Code']}
description={translate(`workspace.tags.glCode`)}
onPress={navigateToEditGlCode}

OPTIONAL: We can also display the not found page for TagGLCodePage if we've connected to an accounting.

We can do the same fix for category GL code if we should also not allow adding them.

What alternative solutions did you explore? (Optional)

If we only don't allow adding GL code for tag when we connected to Netsuite, we can update the hasAccountingConnections check to only return true if we connected to Netsuite

@RachCHopkins

This comment was marked as off-topic.

@RachCHopkins
Copy link
Contributor

Posted in Wave-Control channel for some clarity. https://expensify.slack.com/archives/C06ML6X0W9L/p1726160568530669

@dylanexpensify dylanexpensify moved this to Release 3: Fall 2024 (Nov) in [#whatsnext] #expense Sep 18, 2024
@dylanexpensify dylanexpensify moved this from Release 3: Fall 2024 (Nov) to Tracking in [#whatsnext] #expense Sep 18, 2024
@dylanexpensify dylanexpensify moved this from Tracking to Polish in [#whatsnext] #expense Sep 18, 2024
@RachCHopkins
Copy link
Contributor

We have a number of problems here, just confirming if I need to separate them out on to two more bug reports.

@RachCHopkins
Copy link
Contributor

Ok, I have done two more bug reports, so we can just focus on the appending tags here.

@RachCHopkins
Copy link
Contributor

Ok, I can reproduce this now. I got this wrong. It's not appending manual tags, it's allowing you to edit the GL code.

The expected result here is that when a tag is imported, the GL code field should not be editable, even if it is blank. It is not editable in Expensify classic.

It's correct that it should not persist after a sync, because the code does not come in via the sync.

@RachCHopkins RachCHopkins changed the title Workspace connected to integration (NetSuite) should not allow appending of manual Tags Workspace connected to integration (NetSuite) should not allow editing of GL codes on imported tags. Sep 20, 2024
@RachCHopkins RachCHopkins added the External Added to denote the issue can be worked on by a contributor label Sep 20, 2024
@melvin-bot melvin-bot bot changed the title Workspace connected to integration (NetSuite) should not allow editing of GL codes on imported tags. [$250] Workspace connected to integration (NetSuite) should not allow editing of GL codes on imported tags. Sep 20, 2024
Copy link

melvin-bot bot commented Sep 20, 2024

Job added to Upwork: https://www.upwork.com/jobs/~021836971613968760708

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Sep 20, 2024
Copy link

melvin-bot bot commented Sep 20, 2024

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

@RachCHopkins
Copy link
Contributor

Commenting re the proposal above - this is relevant to all connections, not just NetSuite.

@c3024
Copy link
Contributor

c3024 commented Sep 21, 2024

@mkzie2's proposal looks good to me.

It should be applied for all connections as specified above.

OPTIONAL: We can also display the not found page for TagGLCodePage if we've connected to an accounting.

Agreed.

I think we should not allow editing GL codes for Categories also as suggested in his proposal. This needs to be confirmed.

🎀 👀 🎀 C+ Reviewed

Copy link

melvin-bot bot commented Sep 21, 2024

Triggered auto assignment to @francoisl, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@melvin-bot melvin-bot bot added Overdue and removed Help Wanted Apply this label when an issue is open to proposals by contributors labels Sep 23, 2024
Copy link

melvin-bot bot commented Sep 23, 2024

📣 @c3024 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

Copy link

melvin-bot bot commented Sep 23, 2024

📣 @mkzie2 You have been assigned to this job!
Please apply to the Upwork job and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Once you apply to this job, your Upwork ID will be stored and you will be automatically hired for future jobs!
Keep in mind: Code of Conduct | Contributing 📖

@mkzie2
Copy link
Contributor

mkzie2 commented Sep 24, 2024

@c3024 The PR is ready

@RachCHopkins
Copy link
Contributor

Automation is borked on this.

@c3024 what's the payment date on this one? Can you do the checklist please?

@mkzie2 did you have an offer to accept in Upwork?

@c3024
Copy link
Contributor

c3024 commented Sep 30, 2024

  • [@c3024] The PR that introduced the bug has been identified. Link to the PR: Tags - Add GL Code #43155
  • [@c3024] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/43155/files#r1780496384
  • [@c3024] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: No discussion was started because this could not have been identified earlier.
  • [@c3024] Determine if we should create a regression test for this bug. Yes
  • [@c3024] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression test proposal

  1. Create a workspace
  2. Click on "More features" in the workspace settings page left hand panel
  3. Scroll down and go to "Organize" section and switch on the "Tags" switch
  4. Scroll down and switch the "Accounting" switch to on
  5. Click on "Accounting" from the left hand panel
  6. Click on "Netsuite"
  7. Upgrade the workspace to Control if prompted
  8. Complete the "Netsuite" connection flow
  9. Click on the 3 dot menu on the "Netsuite" account added and click on "Sync now"
  10. Go to "Tags" and click on any tag
  11. Verify that the GL code option is disabled in the opened tag settings page

@c3024
Copy link
Contributor

c3024 commented Sep 30, 2024

Payment is due on 4-Oct.

@mkzie2
Copy link
Contributor

mkzie2 commented Sep 30, 2024

@mkzie2 did you have an offer to accept in Upwork?

@RachCHopkins Hi not yet, can you please send the offer to my account https://www.upwork.com/freelancers/~019f73367b03c6d784

Thanks in advance

@RachCHopkins
Copy link
Contributor

Offer sent @mkzie2

@mkzie2
Copy link
Contributor

mkzie2 commented Oct 1, 2024

@RachCHopkins I have accepted

@RachCHopkins
Copy link
Contributor

Thanks @mkzie2 will action the payment on the 4th!

@RachCHopkins RachCHopkins changed the title [$250] Workspace connected to integration (NetSuite) should not allow editing of GL codes on imported tags. [Payment Due 4 Oct] [$250] Workspace connected to integration (NetSuite) should not allow editing of GL codes on imported tags. Oct 1, 2024
@RachCHopkins
Copy link
Contributor

Payment Summary:

  • Contributor: @mkzie2 to be paid $250 via Upwork
  • Contributor+: @c3024 to be paid $250 via Upwork

Upwork job here

@RachCHopkins
Copy link
Contributor

Contributors have been paid, the contracts have been completed, and the Upwork post has been closed.

@github-project-automation github-project-automation bot moved this from Polish to Done in [#whatsnext] #expense Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. External Added to denote the issue can be worked on by a contributor Reviewing Has a PR in review Weekly KSv2
Projects
Archived in project
Development

No branches or pull requests

6 participants