[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 pull request validation workflow by adding the jira-user-email input. The Atlassian API, used by the linter, requires both an email and an API token for authentication. The absence of the email was causing all Jira ticket lookups to fail, effectively disabling the check.

Files Changed Analysis

• File: .github/workflows/jira-pr-validator.yaml
• Changes: 1 line added, 0 deleted.
• Summary: The change is minimal and confined to a single GitHub Actions workflow configuration file, adding a necessary parameter for authentication.

Architecture & Impact Assessment

• What this PR accomplishes: It restores the functionality of the Jira PR validation linter, which ensures that pull request titles are correctly linked to a valid Jira ticket.

• Key technical changes introduced: A single line, jira-user-email: ${{ secrets.JIRA_USER_EMAIL }}, has been added to the jira-pr-validator.yaml workflow. This provides the Jira linter action with the required email for authentication against the Jira API.

• Affected system components: The change impacts the repository's CI/CD pipeline, specifically the automated checks that run on pull requests. 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 developer workflow within this GitHub repository. By fixing the Jira linter, it ensures that all future pull requests will be correctly validated for a corresponding Jira ticket, improving project tracking and adherence to development processes.
• No further code exploration is necessary, as the change is self-contained within the workflow definition and its purpose is clearly stated and understood.

Metadata

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

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:15:35.938Z | Triggered by: pr_opened | Commit: aa6e711

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

[probelabs]

✅ Security Check Passed

No security issues found – changes LGTM.

---

Powered by Visor from Probelabs

Last updated: 2026-04-16T16:15:24.359Z | Triggered by: pr_opened | Commit: aa6e711

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

[github-actions]

API Changes

no api changes detected

[sonarqubecloud]

Quality Gate failed

Failed conditions
1 Security Hotspot
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[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: aa6e711
Failed at: 2026-04-17 05:20:57 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.