remove redundant parameter from vulnerability retrieval in Jira workf…

[kooomix]

User description

…lows

---

PR Type

Bug fix

---

Description

• Removed redundant parameter expected_results from get_vulns_v2 call.

• Simplified vulnerability retrieval logic in Jira workflows.

---

Changes walkthrough 📝

	Relevant files
Bug fix	jira_workflows.py Simplify vulnerability retrieval logic in tests                    tests_scripts/workflows/jira_workflows.py Removed the expected_results parameter from get_vulns_v2 call. Adjusted logic for vulnerability Jira ticket creation. +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ No major issues detected

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Ensure consistent test behavior by validating the number of vulnerabilities returned from the API call Add pagination handling or result limit validation since the expected_results parameter was removed from get_vulns_v2. Without limiting results, the function might return more vulnerabilities than expected, potentially affecting the test's reliability. tests_scripts/workflows/jira_workflows.py [119] response_vuln = self.backend.get_vulns_v2(body=vuln_body, enrich_tickets=True) +assert len(response_vuln) == 1, f"Expected 1 vulnerability, but got {len(response_vuln)}" Apply this suggestion Suggestion importance[1-10]: 9 Why: The removal of 'expected_results=1' parameter could lead to test inconsistency if multiple vulnerabilities are returned. Adding result count validation is crucial for maintaining test reliability and preventing false positives.	9

[github-actions]

Failed to generate code suggestions for PR