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.

Sign up for GitHub

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

Jump to bottom

Invoice, shipping, credit memo records missing, when archive orders are restored to order management #36847

Closed
github-jira-sync-bot opened this issue Feb 10, 2023 · 12 comments
Closed

Invoice, shipping, credit memo records missing, when archive orders are restored to order management #36847

github-jira-sync-bot opened this issue Feb 10, 2023 · 12 comments
Assignees
@veloraven
Labels
Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Low Priority Backlog

Comments

@github-jira-sync-bot
Copy link

ISSUE:
If an order is moved to the archive and then restored, if the ID numbers don't match, then invoice, shipping, credit memo records are missing from that order.

STEPS TO REPLICATE:

  1. Create and complete an order, including Shipping, Invoice and Credit Memo.
  2. Ensure the Shipping, Invoice and Credit memo IDs are not the same as the order number.
  3. Move the order to Archive
  4. Restore the archived order to Order Management.
  5. Check Invoice, Shipping and Credit Memo details under respective "Invoice", "Shipping"
    , "Credit Memo" - 'We couldn't find any records.'

ACTUAL RESULTS:
'We couldn't find any records.' for Shipping, Invoice and Credit Memo for restored orders if all the IDs are different.
If the order and related records have the same ID, then the records are returned.

EXPECTED RESULTS:
The original related records should be restored when the order is moved from archive list to order management.
@github-jira-sync-bot github-jira-sync-bot added Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: PR in progress Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Feb 10, 2023
@github-jira-sync-bot
Copy link
Author

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1597

@m2-assistant
Copy link

m2-assistant bot commented Feb 10, 2023

Hi @github-jira-sync-bot. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues 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 issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@m2-community-project m2-community-project bot added this to Ready for Development in Low Priority Backlog Feb 10, 2023
@veloraven
Copy link
Contributor

Internal team is working o9n this issue

@veloraven
Copy link
Contributor

@magento I am working on this

@m2-community-project m2-community-project bot moved this from Ready for Development to Dev In Progress in Low Priority Backlog Feb 10, 2023
@raquelperez899
Copy link

@magento give me 2.4.5-p1 instance

@magento-deployment-service
Copy link

Hi @raquelperez899. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

Hi @raquelperez899, here is your Magento Instance: https://74a5e1a01ea8d56859afadb46b209fbf.instances.magento-community.engineering
Admin access: https://74a5e1a01ea8d56859afadb46b209fbf.instances.magento-community.engineering/admin_0bcd
Login: c70f9ec9
Password: a86d0bdbf6eb

@m2-community-project m2-community-project bot moved this from Dev In Progress to Pull Request In Progress in Low Priority Backlog Feb 25, 2023
@magento-deployment-service
Copy link

Hi @raquelperez899, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

@raquelperez899
Copy link

@magento give me 2.4.5-p1 instance

@magento-deployment-service
Copy link

Hi @raquelperez899. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

Hi @raquelperez899, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Done in Low Priority Backlog Apr 10, 2023
@chittima
Copy link
Contributor

chittima commented Sep 8, 2023

Closed since it not community edition functionality

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@veloraven veloraven

Labels
Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Low Priority Backlog
  
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@veloraven @chittima @github-jira-sync-bot @raquelperez899