Skip to content

Adding the company and VAT Number values at OPC address. #31425

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

Closed

Conversation

rav-redchamps
Copy link
Contributor

@rav-redchamps rav-redchamps commented Dec 23, 2020

Description (*)

Adding the company and VAT Number values at OPC address.

Related Pull Requests

https://github.com/magento/partners-magento2b2b/pull/538

Fixed Issues (if relevant)

N/A

Manual testing scenarios (*)

  1. Enable showing company and VAT Number data at the front
  2. Check if it is available at OPC.

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

Resolved issues:

  1. resolves [Issue] Region data fix #31439: Region data fix

Resolved issues:

  1. resolves [Issue] Adding the company and VAT Number values at OPC address. #31652: Adding the company and VAT Number values at OPC address.

@m2-assistant
Copy link

m2-assistant bot commented Dec 23, 2020

Hi @rav-redchamps. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@rav-redchamps
Copy link
Contributor Author

@magento run all tests

@sidolov sidolov added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Dec 23, 2020
@sidolov
Copy link
Contributor

sidolov commented Dec 23, 2020

@magento create issue

@m2-assistant m2-assistant bot mentioned this pull request Dec 23, 2020
4 tasks
Copy link
Contributor

@sidolov sidolov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rav-redchamps please, cover changes with an automated test. Thanks!

@engcom-Hotel
Copy link
Contributor

engcom-Hotel commented Dec 24, 2020

Hello @rav-redchamps,
The fix already exists at #27608
So, we may continue the current PR partially.
Like 'adding the company and VAT Number values at the checkout'.
Steps to reproduce:
Magento version: 2.4-develop
PHP version: 7.4
ElasticSearch version: 7
MySQL version: 8.0

  1. Set Store->Configuration->Customer Configuration->Create New Account Options->Show Company to 'Optional'
  2. Set Store->Configuration->Customer Configuration->Create New Account Options->Show VAT Number on Storefront to 'Optional'
  3. Save config
  4. bin/magento c:c
  5. Open registration page /customer/account/create/
  6. Create the customer with the company name and add VAT Number (admin->Customers->edit created customer->Addresses->Add/Update Address)
  7. Add any product to the cart and check if company name and VAT Id are visible at checkout/#shipping and checkout/#payment (both payment and shipment areas)
    Thank you.

PS. I will help with the test coverage

@engcom-Hotel
Copy link
Contributor

@magento run all tests

@engcom-Hotel
Copy link
Contributor

@magento run Functional Tests CE

1 similar comment
@engcom-Hotel
Copy link
Contributor

@magento run Functional Tests CE

@engcom-Hotel
Copy link
Contributor

Hi @sidolov,
This PR is a duplicate of #27608.
We can recreate the issue for "adding the company and VAT Number values at OPC" and update the priority for it.
Could you please have a look?
Thank you.

@sidolov
Copy link
Contributor

sidolov commented Jan 4, 2021

@engcom-Hotel not sure how they are related, current PR going to display fields in case the address object has them and the second one aimed to support the region selector on the page

@sidolov sidolov added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. and removed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. labels Jan 5, 2021
@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@Den4ik
Copy link
Contributor

Den4ik commented May 27, 2021

@engcom-Foxtrot Looks like after creating the product we should run reindex because product page is not available

@engcom-Foxtrot
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

2 similar comments
@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Foxtrot
Copy link
Contributor

@magento run Functional Tests CE, Functional Tests B2B

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Charlie engcom-Charlie self-assigned this Sep 8, 2021
@engcom-Charlie
Copy link
Contributor

Hi @rav-redchamps,

Thank you for your contribution.

I am working on the suggested review changes.

Thank you!

@engcom-Charlie
Copy link
Contributor

@magento run Functional Tests CE, Functional Tests B2B

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

1 similar comment
@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Charlie
Copy link
Contributor

Thank you everyone for your contribution!

It seems that the review changes has been taken care with new MFTF test case.

I have tested the new MFTF test case and its working fine.

Also found that the test case which is failing in this build is not part of this PR. Its failing because of customer search is not working and not because of PR changes. So kindly asking for review again.

@engcom-Foxtrot, I was about to merge the 2.4-develop branch to PR branch before passing it to review, but found that you have merge 2.4-develop-mainline into this branch. Curious to know why 2.4-develop-mainline was got merged.

@engcom-Charlie
Copy link
Contributor

@engcom-Foxtrot can you please provide any details on this comment. It will be helpful to move this issue further.

Thank you!

@engcom-Charlie
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds.

@Den4ik
Copy link
Contributor

Den4ik commented Oct 17, 2021

@magento run all tests

@magento-automated-testing
Copy link

Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds.

@engcom-Charlie
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds.

@engcom-Charlie
Copy link
Contributor

As per comment, the test case which is failing in this build is not part of this PR. Its failing because of customer search is not working in PR branch.

In order to move this issue further, I have to merge the latest 2.4 develop code base in this branch but as I have mentioned in this comment, @engcom-Foxtrot have merge the 2.4-develop-mainline branch to PR branch which might be causing this failure.

To make a good progress, I will be raising a new PR for this issue and close this PR.

Thank you!

@engcom-Charlie
Copy link
Contributor

Created new PR so closing this PR now

Thank you!

@m2-assistant
Copy link

m2-assistant bot commented Oct 19, 2021

Hi @rav-redchamps, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: Checkout Component: Customer Priority: P2 A defect with this priority could have functionality issues which are not to expectations. QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Issue] Adding the company and VAT Number values at OPC address. [Issue] Region data fix
9 participants