Skip to content

chore: add jira to issue template [SWC-580] #5459

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

castastrophe
Copy link
Collaborator

Description

I expect to see a new checkbox at the bottom of each of the following templates allowing users to receiving a Jira ticket notification:

  • bug_report.yaml
  • feature_request.yaml
  • new_component.yaml
  • general.yaml

Related issue(s)

  • fixes [SWC-580]

Author's checklist

  • I have read the CONTRIBUTING and PULL_REQUESTS documents.
  • [n/a] I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
  • [n/a] I have added automated tests to cover my changes.
  • [n/a] I have included a well-written changeset if my change needs to be published.
  • [n/a] I have included updated documentation if my change required it.

Reviewer's checklist

  • Includes a Github Issue with appropriate flag or Jira ticket number without a link
  • Includes thoughtfully written changeset if changes suggested include patch, minor, or major features
  • Automated tests cover all use cases and follow best practices for writing
  • Validated on all supported browsers
  • All VRTs are approved before the author can update Golden Hash

Manual review test cases

Once merged to main, we can validate this update worked by attempting to open each of the updated issue templates and see an additional Jira checkbox at the end.

@castastrophe castastrophe requested a review from a team as a code owner May 8, 2025 16:07
Copy link

changeset-bot bot commented May 8, 2025

⚠️ No Changeset found

Latest commit: 7dc3d86

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@castastrophe castastrophe self-assigned this May 8, 2025
@castastrophe castastrophe added ready-for-review Tooling Administrative an organisational/administrative issue github_actions Pull requests that update GitHub Actions code labels May 8, 2025
Copy link

github-actions bot commented May 8, 2025

Branch preview

Review the following VRT differences

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

Copy link

github-actions bot commented May 8, 2025

Tachometer results

Currently, no packages are changed by this PR...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Administrative an organisational/administrative issue github_actions Pull requests that update GitHub Actions code ready-for-review Tooling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants