This PR updates the intelligent-branch-recomendations.yml GitHub Actions workflow. The changes involve updating the commit hash for the reusable branch-suggestion.yml workflow and modifying the secrets used for Jira authentication.

Files Changed Analysis

• File: .github/workflows/intelligent-branch-recomendations.yml
• Changes: 3 additions, 2 deletions.
• Summary: The changes are confined to a single CI/CD workflow file. The modifications update a reusable workflow reference and change the authentication secrets being passed to it.

Architecture & Impact Assessment

• What this PR accomplishes: It aligns the repository's branch suggestion workflow with an updated, centralized version. This involves adopting a new method for Jira authentication, replacing a single JIRA_TOKEN with JIRA_READ_AUTH and JIRA_BASE_URL.

• Key technical changes:

  1. The uses clause for the branch-suggestion.yml workflow is updated to a new commit hash (c0d4c3d...).
  2. The secrets passed to the workflow have been changed from JIRA_TOKEN to JIRA_READ_AUTH and JIRA_BASE_URL.

• Affected system components: The change impacts the CI/CD pipeline, specifically the developer tooling that suggests branch names based on Jira tickets. There is no impact on the production application code.

• Workflow Diagram:

  graph TD
      A[This Repo: intelligent-branch-recomendations.yml] -- calls --> B["Reusable Workflow: TykTechnologies/github-actions/branch-suggestion.yml@c0d4c3d"];
      B -- uses secrets --> C{JIRA_READ_AUTH & JIRA_BASE_URL};
      B -- to authenticate with --> D[Jira API];
  
  

  Loading

### Scope Discovery & Context Expansion
- The immediate scope is limited to this repository's CI configuration. However, this change implies a broader, organization-wide update to the `TykTechnologies/github-actions` reusable workflow.
- The updated commit hash in `branch-suggestion.yml` likely contains the logic requiring the new `JIRA_READ_AUTH` and `JIRA_BASE_URL` secrets. This suggests a move towards a more standardized and possibly more secure way of authenticating with Jira across multiple repositories that use this shared action.
- Other repositories within the organization using the same reusable workflow will likely require a similar update to remain functional.


<details>
  <summary>Metadata</summary>

  - Review Effort: 1 / 5
  - Primary Label: chore


</details>
<!-- visor:section-end id="overview" -->

<!-- visor:thread-end key="TykTechnologies/tyk#8213@38a4da5" -->

---

*Powered by [Visor](https://probelabs.com/visor) from [Probelabs](https://probelabs.com)*

*Last updated: 2026-05-13T11:49:39.846Z | Triggered by: pr_opened | Commit: 38a4da5*

💡 **TIP:** You can chat with Visor using `/visor ask <your question>`
<!-- /visor-comment-id:visor-thread-overview-TykTechnologies/tyk#8213 -->

🎯 Recommended Merge Targets

Based on JIRA ticket TT-17162: Use scoped Jira API tokens for branch suggestion workflow

Fix Version: Tyk 5.8.15

Required:

• release-5.8 - Minor version branch for 5.8.x patches - required for creating Tyk 5.8.15
• master - Main development branch - ensures fix is in all future releases

📋 Workflow

1. Merge this PR to master first

2. Cherry-pick to release branches by commenting on the merged PR:

   • /release to release-5.8

3. Automated backport - The bot will automatically create backport PRs to the specified release branches

✅ Architecture Check Passed

No architecture issues found – changes LGTM.

✅ Performance Check Passed

No performance issues found – changes LGTM.

✅ 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-05-13T11:49:27.441Z | Triggered by: pr_opened | Commit: 38a4da5

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

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