fix: add jira-user-email to Jira linter workflow [TT-16950]

[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

Test plan

• Verify the Jira linter check passes on a PR with a valid Jira ticket reference

🤖 Generated with Claude Code

[probelabs]

This pull request fixes a bug in the Jira pull request validation workflow.

Files Changed Analysis

• File: .github/workflows/jira-pr-validator.yaml
• Changes: 1 line added.
• The change introduces the jira-user-email input to the TykTechnologies/jira-linter GitHub Action, sourced from a repository secret.

Architecture & Impact Assessment

• What this PR accomplishes: It resolves an authentication issue with the Atlassian API in the CI pipeline. The Jira linter action was previously failing because it lacked the user email required for basic authentication, causing all Jira ticket lookups to fail.
• Key technical changes introduced: A single line is added to the .github/workflows/jira-pr-validator.yaml file, providing the jira-user-email to the linter action.
• Affected system components: The change impacts only the repository's CI/CD developer workflow. It has no effect on the application's runtime behavior or architecture. The fix ensures that pull requests are correctly validated against Jira tickets.

Scope Discovery & Context Expansion

• The scope of this change is confined to the GitHub Actions workflow for this repository. It corrects a process issue, ensuring that the automated check for valid Jira ticket references in PR titles functions correctly.
• No other parts of the codebase are affected. This is a self-contained fix for a CI workflow configuration.

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:12:32.935Z | Triggered by: pr_opened | Commit: 2c71c63

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

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Security Check Passed

No security issues found – changes LGTM.

\n\n

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

\n\n \n\n

✅ Quality Check Passed

No quality issues found – changes LGTM.

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:12:26.642Z | Triggered by: pr_opened | Commit: 2c71c63

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

[github-actions]

API Changes

no api changes detected

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[buger]

Closing: investigation confirmed jira-user-email input is declared but never consumed by the linter code.

[buger]

Reopening: jira-user-email IS required — the action.yaml has required: true and passes it as JL_JIRA_USEREMAIL env var.

[github-actions]

🚨 Jira Linter Failed

Commit: 2c71c63
Failed at: 2026-04-17 05:20:36 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-master' 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.