[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 pull request fixes a bug in the jira-pr-validator GitHub Actions workflow by adding the required jira-user-email input. The Atlassian API needs both a user email and an API token for authentication, and the missing email was causing all Jira ticket lookups to fail.

Files Changed Analysis

• .github/workflows/jira-pr-validator.yaml: A single line was added to supply the JIRA_USER_EMAIL secret to the jira-linter action, enabling proper authentication.

Architecture & Impact Assessment

• What this PR accomplishes: It repairs the automated CI check that validates Jira ticket references in pull request titles, which was previously failing due to an authentication error.
• Key technical changes introduced: The jira-user-email parameter is now passed to the TykTechnologies/jira-linter action, using a value from GitHub secrets.
• Affected system components: The change is confined to the repository's CI/CD pipeline. It has no impact on the application's runtime code or architecture.

Scope Discovery & Context Expansion

• The scope of this change is limited to the repository's developer workflow. By fixing the Jira linter, it ensures that pull requests are correctly linked to Jira tickets, improving project tracking and traceability.
• No other parts of the codebase are affected. The fix is isolated to this specific workflow configuration.

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:15:08.657Z | Triggered by: pr_opened | Commit: 042f683

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

[probelabs]

\n\n

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

✅ Quality Check Passed

No quality issues found – changes LGTM.

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:15:06.257Z | Triggered by: pr_opened | Commit: 042f683

💡 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: 042f683
Failed at: 2026-04-17 16:48:54 UTC

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

🔍 Click to view error details

failed to get Jira issue: failed to fetch Jira issue TT-16977: Issue does not exist or you do not have permission to see it.: request failed. Please analyze the request body for more details. Status code: 404

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.