fix: add jira-user-email to Jira linter workflow #8050
Closed
probelabs / Visor: quality
failed
Apr 16, 2026 in 1m 4s
🚨 Check Failed
quality check failed because fail_if condition was met.
Details
📊 Summary
- Total Issues: 2
- Error Issues: 2
🔍 Failure Condition Results
Failed Conditions
- global_fail_if: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
- Severity: ❌ error
Issues by Category
Logic (2)
- ❌ .github/workflows/jira-pr-validator.yaml:27 - The code change shown in the diff appears to be a no-op, replacing a line with an identical one. This does not align with the PR's description, which states the goal is to add the
jira-user-emailinput to fix a failing Jira integration. The intended fix seems to be missing from this pull request. - ❌ system:0 - Global failure condition met: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check failure on line 27 in .github/workflows/jira-pr-validator.yaml
probelabs / Visor: quality
logic Issue
The code change shown in the diff appears to be a no-op, replacing a line with an identical one. This does not align with the PR's description, which states the goal is to add the `jira-user-email` input to fix a failing Jira integration. The intended fix seems to be missing from this pull request.
Raw output
Update the pull request to include the necessary `jira-user-email` input for the `TykTechnologies/jira-linter` action. Based on the PR description, a line should be added for the user email, for example: `jira-user-email: ${{ secrets.JIRA_USER_EMAIL }}` (assuming that is the correct secret name).
Loading