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

B2B Company mutations - Update company hierarchy #29095

Closed
pmarjan opened this issue Jul 13, 2020 · 3 comments · Fixed by #29426
Closed

B2B Company mutations - Update company hierarchy #29095

pmarjan opened this issue Jul 13, 2020 · 3 comments · Fixed by #29426
Assignees
Labels
B2B: GraphQL feature request Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed PAP Partners acceleration program Project: GraphQL
Milestone

Comments

@pmarjan
Copy link
Contributor

pmarjan commented Jul 13, 2020

Description (*)

Partially solves #28867

Update company hierarchy

Expected behavior (*)

Benefits

Additional information

@pmarjan pmarjan added this to the 2.4.1 milestone Jul 13, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jul 13, 2020

Hi @pmarjan. 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.

Please, add a comment to assign the issue: @magento I am working on this


⚠️ 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, 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

@ghost ghost added this to Ready for QA in Community Backlog Jul 13, 2020
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jul 13, 2020
@nrkapoor nrkapoor moved this from Ready for QA to Ready for Dev in Community Backlog Jul 14, 2020
@pmarjan pmarjan self-assigned this Jul 17, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jul 17, 2020

Hi @pmarjan. 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.
    1. 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.
    1. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
    1. 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!

@ghost ghost moved this from Ready for Dev to Dev in Progress in Community Backlog Jul 17, 2020
@ghost ghost moved this from Dev in Progress to PR In Progress in Community Backlog Jul 20, 2020
@nrkapoor nrkapoor modified the milestones: 2.4.1, 2.4.2 Aug 11, 2020
@m2-assistant
Copy link

m2-assistant bot commented Aug 12, 2020

Hi @gallyamov. 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.
    1. 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.
    1. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
    1. 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!

@ghost ghost unassigned pmarjan Aug 13, 2020
@gallyamov gallyamov moved this from PR In Progress to Dev in Progress in Community Backlog Aug 13, 2020
@ghost ghost moved this from Dev in Progress to PR In Progress in Community Backlog Aug 13, 2020
@gallyamov gallyamov linked a pull request Aug 13, 2020 that will close this issue
4 tasks
@ghost ghost moved this from PR In Progress to Done (last 30 days) in Community Backlog Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B2B: GraphQL feature request Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed PAP Partners acceleration program Project: GraphQL
Projects
No open projects
Community Backlog
  
Done (last 30 days)
Development

Successfully merging a pull request may close this issue.

4 participants