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

Test Jira Import #39520

Closed
5 tasks
nathanjosiah opened this issue Jan 3, 2025 · 15 comments
Closed
5 tasks

Test Jira Import #39520

nathanjosiah opened this issue Jan 3, 2025 · 15 comments
Labels
Area: Security Component: Ui Issue: ready for confirmation Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S1 Affects critical data or functionality and forces users to employ a workaround.

Comments

@nathanjosiah
Copy link
Contributor

Preconditions and environment

  • Magento version
  • Anything else that would help a developer reproduce the bug

Steps to reproduce

test test

Expected result

test

Actual result

test

Additional information

No response

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented Jan 3, 2025

Hi @nathanjosiah. 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 Jan 3, 2025
@nathanjosiah
Copy link
Contributor Author

@magento export issue to Jira project AC as Bug

@nathanjosiah
Copy link
Contributor Author

@adobe export issue to Jira project AC as Bug

@github-jira-sync-bot
Copy link

❌ Something went wrong. Cannot create Jira issue.

1 similar comment
@github-jira-sync-bot
Copy link

❌ Something went wrong. Cannot create Jira issue.

@nathanjosiah
Copy link
Contributor Author

@adobe export issue to Jira project AC as Bug

@github-jira-sync-bot
Copy link

❌ Something went wrong. Cannot create Jira issue.

@nathanjosiah
Copy link
Contributor Author

@adobe export issue to Jira project AC as Bug

@github-jira-sync-bot
Copy link

❌ Something went wrong. Cannot create Jira issue.

@nathanjosiah nathanjosiah added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Severity: S1 Affects critical data or functionality and forces users to employ a workaround. labels Jan 8, 2025
@nathanjosiah
Copy link
Contributor Author

@adobe export issue to Jira project AC as Bug

@github-jira-sync-bot
Copy link

❌ Something went wrong. Cannot create Jira issue.

@nathanjosiah nathanjosiah added the Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch label Jan 8, 2025
@nathanjosiah nathanjosiah moved this from Ready for Confirmation to Confirmed in Issue Confirmation and Triage Board Jan 8, 2025
@nathanjosiah
Copy link
Contributor Author

@adobe export issue to Jira project AC as Bug

@github-jira-sync-bot
Copy link

❌ Something went wrong. Cannot create Jira issue.

@nathanjosiah
Copy link
Contributor Author

@adobe export issue to Jira project AC as Bug

@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-13659 is successfully created for this GitHub issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Security Component: Ui Issue: ready for confirmation Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S1 Affects critical data or functionality and forces users to employ a workaround.
Projects
Issue Confirmation and Triage Board
Status: Confirmed
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nathanjosiah @github-jira-sync-bot