Skip to content

Conversation

@antonio-rmrz
Copy link
Collaborator

Resolves https://jira.corp.adobe.com/browse/MWPW-184913
QA Checklist: https://wiki.corp.adobe.com/display/adobedotcom/M@S+Engineering+QA+Use+Cases

  • Automatically links GitHub PRs to Jira tickets when a PR is opened
  • Extracts Jira ticket IDs (e.g., MWPW-12345) from PR title or branch name
  • Verifies the ticket exists in Jira before creating the link
  • Creates a remote link in Jira pointing back to the PR with format [repo] PR #Number: Title
  • Skips gracefully if no ticket ID found or link already exists

Example:

image

Test URLs: N/A

@aem-code-sync
Copy link

aem-code-sync bot commented Jan 5, 2026

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch.
In case there are problems, just click the checkbox below to rerun the respective action.

  • Re-sync branch
Commits

@antonio-rmrz antonio-rmrz requested a review from Roycethan January 6, 2026 02:46
@antonio-rmrz antonio-rmrz changed the title MWPW-184913: Workflow to automatically attach Github PR Link to Jira issues MWPW-184913: Workflow to automaticaly attach Github PR Link to Jira issues Jan 6, 2026
@antonio-rmrz antonio-rmrz changed the title MWPW-184913: Workflow to automaticaly attach Github PR Link to Jira issues MWPW-184913: Workflow to automatically attach Github PR Link to Jira issues Jan 6, 2026
@antonio-rmrz antonio-rmrz changed the title MWPW-184913: Workflow to automatically attach Github PR Link to Jira issues MWPW-184913: Auto-link PRs to Jira tickets Jan 6, 2026
Copy link
Contributor

@honstar honstar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great 👍

@antonio-rmrz antonio-rmrz requested a review from yesil January 6, 2026 16:56
Copy link
Member

@Axelcureno Axelcureno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

Copy link
Contributor

@npeltier npeltier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great! i wonder to what extent while we are at it, we shouldn't fail the PR if the title doesn't fit a certain pattern.
of course, there are those that should be dealt with #506 but probably better if that one would have JIRA ticket as well to track effort there as well

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants