Skip to content

My account Address Book Additional Address Entries table issue #27335

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
abrarpathan19 opened this issue Mar 18, 2020 · 5 comments
Closed

My account Address Book Additional Address Entries table issue #27335

abrarpathan19 opened this issue Mar 18, 2020 · 5 comments
Assignees
Labels
Area: Design/Frontend Component: Customer Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reported on 2.3.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@abrarpathan19
Copy link
Contributor

Preconditions (*)

  1. Magento 2.3

Steps to reproduce (*)

  1. Login to Luma theme front end -> My account -> Address Book -> Address Entries table
  2. see the table head aliment issue in (Tablet, Desktop)

Expected result (*)

  1. https://prnt.sc/rig3rm
  2. https://prnt.sc/rig551

Actual result (*)

  1. https://prnt.sc/rig4f6
  2. https://prnt.sc/rig4oi
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Mar 18, 2020
@m2-assistant
Copy link

m2-assistant bot commented Mar 18, 2020

Hi @abrarpathan19. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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

@abrarpathan19 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

@m2-assistant
Copy link

m2-assistant bot commented Mar 18, 2020

Hi @krishprakash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Add label Issue: Confirmed once verification is complete.

  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@krishprakash krishprakash added Area: Design/Frontend Component: Customer Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Mar 20, 2020
@ghost ghost unassigned krishprakash Mar 20, 2020
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-32606 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Mar 20, 2020
magento-engcom-team added a commit that referenced this issue Mar 21, 2020
… table issue #27335 #27336

 - Merge Pull Request #27336 from abrarpathan19/magento2:27335
 - Merged commits:
   1. 5abd366
magento-engcom-team added a commit that referenced this issue Mar 21, 2020
…op expedited

Accepted Community Pull Requests:
 - #27298: Implement ActionInterface for `cms/page/view` (by @lbajsarowicz)
 - #27116: Add Italy States (by @WaPoNe)
 - #26748: #26745 add method setAdditionalInformation to OrderPaymentInte… (by @antoninobonumore)
 - #27336: fixed My account Address Book Additional Address Entries table issue #27335 (by @abrarpathan19)
 - #27263: #26708 Fix: ORDER BY has two similar conditions in the SQL query (by @vasilii-b)
 - #27304: FIX #14080 Added improvements to Category repository (save method) (by @sergiy-v)
 - #27214: Mark AbstractAccount as DEPRECATED for Magento_Customer controllers (by @lbajsarowicz)
 - #27292: Magento_Bundle / Remove `cache:flush` and extract Tests to separate files (by @lbajsarowicz)


Fixed GitHub Issues:
 - #26708: ORDER BY has two similar conditions (reported by @Usik2203) has been fixed in #27263 by @vasilii-b in 2.4-develop branch
   Related commits:
     1. 1e1ebd3
     2. df35dda
     3. b816334
     4. a61d92a
@sdzhepa
Copy link
Contributor

sdzhepa commented Apr 30, 2020

The issue has been fixed in #27336

@sdzhepa sdzhepa closed this as completed Apr 30, 2020
@magento-engcom-team magento-engcom-team added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label May 1, 2020
@magento-engcom-team
Copy link
Contributor

Hi @abrarpathan19. Thank you for your report.
The issue has been fixed in #27336 by @abrarpathan19 in 2.4-develop branch
Related commit(s):

The fix will be available with the upcoming 2.4.0 release.

@magento-engcom-team magento-engcom-team added the Reported on 2.3.x Indicates original Magento version for the Issue report. label Nov 13, 2020
This was referenced May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Design/Frontend Component: Customer Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reported on 2.3.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
None yet
Development

No branches or pull requests

4 participants