fix: add jira-user-email to Jira linter workflow

[buger]

Summary

• Adds missing `jira-user-email` input to the Jira PR validator workflow
• The Atlassian API requires both email and token for basic auth
• Without this, all Jira ticket lookups fail with 404

🤖 Generated with Claude Code

[github-actions]

🚨 Jira Linter Failed

Commit: ff23c57
Failed at: 2026-04-16 16:13:28 UTC

The Jira linter failed to validate your PR. Please check the error details below:

🔍 Click to view error details

failed to validate branch and PR title rules: branch name 'fix/jira-linter-email-5.12' must contain a valid Jira ticket ID (e.g., ABC-123)

Next Steps

• Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
• Verify your PR title matches the branch's Jira ticket ID
• Check that the Jira ticket exists and is accessible

---

This comment will be automatically deleted once the linter passes.

[probelabs]

This PR fixes a bug in the jira-pr-validator.yaml GitHub Actions workflow by adding the jira-user-email input. This is required for authentication with the Atlassian API, which needs both an email and an API token. Without this change, Jira ticket lookups in pull requests were failing.

Files Changed Analysis

• .github/workflows/jira-pr-validator.yaml: Modified to include the jira-user-email parameter for the jira-linter action, correcting the authentication configuration.

Architecture & Impact Assessment

• What this PR accomplishes: Restores the functionality of the Jira PR validation workflow, which was failing due to an incomplete authentication configuration.
• Key technical changes introduced: A single line was added to the workflow file to pass the jira-user-email to the TykTechnologies/jira-linter action.
• Affected system components: The change impacts only the repository's CI/CD pipeline. It ensures that the automated check for valid Jira ticket references in pull request titles works correctly. There is no impact on the application's runtime code.

Scope Discovery & Context Expansion

• The scope of this change is confined to the CI process within this repository. It addresses a failure in a specific developer workflow validation step.
• To expand context, a reviewer could verify the action.yml or documentation for the TykTechnologies/jira-linter action to confirm the requirement for jira-user-email. It would also be prudent to check if other workflows in the .github/workflows/ directory use this action and might require a similar update.

Metadata

• Review Effort: 1 / 5
• Primary Label: bug

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:14:42.475Z | Triggered by: pr_opened | Commit: ff23c57

💡 TIP: You can chat with Visor using /visor ask <your question>

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Security Check Passed

No security issues found – changes LGTM.

\n\n

Architecture Issues (1)

Severity	Location	Issue
🟠 Error	.github/workflows/jira-pr-validator.yaml:27	The change in the diff appears to be a no-op, replacing a line with an identical one. This contradicts the pull request title and description, which state that the `jira-user-email` input is being added to fix the Jira linter workflow. The commit does not implement the described change, and therefore the underlying issue will not be resolved. 💡 Suggestion Please amend the commit to correctly add the `jira-user-email` input to the `jira-linter` action's `with` block. The Atlassian API requires both email and token, so this parameter is necessary to fix the workflow as described in the pull request summary.

✅ Performance Check Passed

No performance issues found – changes LGTM.

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:14:26.859Z | Triggered by: pr_opened | Commit: ff23c57

💡 TIP: You can chat with Visor using /visor ask <your question>

[github-actions]

API Changes

no api changes detected