[TT-16977] 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

Test plan

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

🤖 Generated with Claude Code

[probelabs]

This PR fixes a bug in the jira-pr-validator GitHub Actions workflow. The workflow was failing because the jira-user-email input, which is required for authentication by the Atlassian API, was missing. The change adds this parameter, configured to use the JIRA_USER_EMAIL repository secret.

Files Changed Analysis

• File: .github/workflows/jira-pr-validator.yaml
• Change: +1 line, 0 deletions
• Summary: The change is a single-line addition to a CI/CD workflow configuration file. It provides a necessary authentication parameter to a third-party GitHub Action.

Architecture & Impact Assessment

• What this PR accomplishes: It restores the functionality of the Jira linter, which automatically validates that pull request titles contain a valid Jira ticket reference. This ensures adherence to the project's development process.
• Key technical changes introduced: A jira-user-email input has been added to the TykTechnologies/jira-linter action step, sourcing its value from the repository's secrets (secrets.JIRA_USER_EMAIL).
• Affected system components: The change impacts the repository's CI/CD pipeline and developer workflow. It has no effect on the application's runtime code or production environment.

Scope Discovery & Context Expansion

• The scope of this change is limited to the CI/CD process within this repository. By fixing the Jira integration, it ensures that pull requests are correctly linked to Jira tickets before they can be merged, improving project tracking and release management.
• The immediate context is the jira-pr-validator.yaml workflow, which is triggered on pull requests. The fix depends on the JIRA_USER_EMAIL secret being correctly configured in the repository's GitHub settings.

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:15:06.362Z | Triggered by: pr_opened | Commit: ebeae3e

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

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

✅ Security Check Passed

No security issues found – changes LGTM.

\n\n \n\n

✅ Performance Check Passed

No performance issues found – changes LGTM.

\n\n

✅ Quality Check Passed

No quality issues found – changes LGTM.

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:15:04.895Z | Triggered by: pr_opened | Commit: ebeae3e

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

[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.

[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