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

Test Issue - INTERNAL. FOR TESTING PURPOSES ONLY. #39346

Open
orsinijose opened this issue Nov 7, 2024 · 2 comments · May be fixed by #39326
Open

Test Issue - INTERNAL. FOR TESTING PURPOSES ONLY. #39346

orsinijose opened this issue Nov 7, 2024 · 2 comments · May be fixed by #39326

Comments

@orsinijose
Copy link
Collaborator

Preconditions (*)

  1. Testing synch of Issues/PRs with existing Dashboards

Steps to reproduce (*)

  1. Create a test PR on this repo..
  2. Add the label Project: Community Picked to that PR.
  3. Remove label Project: Community Picked to that PR.
  4. Crete an Issue and link it to PR body.
  5. Add the label Project: Community Picked to that PR.

Expected result (*)

  1. See if ticket is added to Community Dashboard

Actual result (*)

  1. will update shortly.
Copy link

m2-assistant bot commented Nov 7, 2024

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


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.

@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Nov 7, 2024
@orsinijose orsinijose linked a pull request Nov 7, 2024 that will close this issue
5 tasks
@orsinijose orsinijose added the Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. label Nov 7, 2024
@orsinijose orsinijose added Priority: P3 May be fixed according to the position in the backlog. Issue: needs update Additional information is require, waiting for response and removed Issue: ready for confirmation Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: PR in progress labels Nov 7, 2024
@orsinijose orsinijose removed the Priority: P3 May be fixed according to the position in the backlog. label Nov 11, 2024
@magento-ct-gh-projects-svc magento-ct-gh-projects-svc moved this from Ready for Confirmation to Confirmed in Issue Confirmation and Triage Board Jan 14, 2025
@orsinijose orsinijose added the Priority: P3 May be fixed according to the position in the backlog. label Jan 22, 2025
@magento-ct-gh-projects-svc magento-ct-gh-projects-svc moved this to Pull Request In Progress in Low Priority Backlog Jan 22, 2025
@magento-ct-gh-projects-svc magento-ct-gh-projects-svc moved this from Pull Request In Progress to Ready for Development in Low Priority Backlog Jan 22, 2025
@orsinijose orsinijose removed the Priority: P3 May be fixed according to the position in the backlog. label Jan 22, 2025
@orsinijose orsinijose reopened this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for Development
Development

Successfully merging a pull request may close this issue.

3 participants