feat: enhance ticket compliance analysis with human verification tracking

[hussam789]

PR Type

Enhancement, Documentation

---

Description

• Enhanced ticket compliance logic with human verification tracking.

• Improved compliance level aggregation and emoji representation.

• Updated documentation for ticket compliance fields in prompts.

---

Changes walkthrough 📝

	Relevant files
Enhancement	utils.py Enhance ticket compliance logic and markdown generation    pr_agent/algo/utils.py Added tracking for human verification in ticket compliance. Enhanced compliance level aggregation logic and emoji representation. Improved error handling and logging for ticket compliance processing. Updated markdown generation for compliance analysis. +85/-34
Documentation	pr_reviewer_prompts.toml Update ticket compliance field documentation                          pr_agent/settings/pr_reviewer_prompts.toml Updated field descriptions for ticket compliance. Added a new field for human verification requirements. Improved clarity and detail in compliance-related documentation. +4/-4

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🏅 Score: 85

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The ticket compliance processing has broad exception handling that may hide specific issues. Consider adding more granular error handling and logging specific error types. except Exception as e: get_logger().exception(f"Failed to process ticket compliance: {e}") continue Code Complexity The compliance level calculation logic has multiple nested conditions that could be simplified or extracted into a separate function for better maintainability. if all_compliance_levels: if all(level == 'Fully compliant' for level in all_compliance_levels): compliance_level = 'Fully compliant' compliance_emoji = '✅' elif all(level == 'PR Code Verified' for level in all_compliance_levels): compliance_level = 'PR Code Verified' compliance_emoji = '✅' elif any(level == 'Not compliant' for level in all_compliance_levels): # If there's a mix of compliant and non-compliant tickets if any(level in ['Fully compliant', 'PR Code Verified'] for level in all_compliance_levels): compliance_level = 'Partially compliant' compliance_emoji = '🔶' else: compliance_level = 'Not compliant' compliance_emoji = '❌' elif any(level == 'Partially compliant' for level in all_compliance_levels): compliance_level = 'Partially compliant' compliance_emoji = '🔶' else: compliance_level = 'PR Code Verified' compliance_emoji = '✅'

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Handle invalid ticket URL safely Add error handling for empty or invalid ticket_url to prevent potential runtime errors when accessing the URL's last segment. pr_agent/algo/utils.py [326-362] ticket_url = ticket_analysis.get('ticket_url', '').strip() -... -ticket_compliance_str += f"\n\n**[{ticket_url.split('/')[-1]}]({ticket_url}) - {ticket_compliance_level}**\n\n{explanation}\n\n" +if not ticket_url: + get_logger().warning("Empty ticket URL found in compliance analysis") + continue +ticket_id = ticket_url.split('/')[-1] if '/' in ticket_url else ticket_url +ticket_compliance_str += f"\n\n**[{ticket_id}]({ticket_url}) - {ticket_compliance_level}**\n\n{explanation}\n\n" Suggestion importance[1-10]: 8 Why: The suggestion addresses a potential runtime error that could occur when processing invalid ticket URLs. Adding proper validation and error handling for empty URLs improves the code's robustness and prevents crashes.	8
	Validate variable before statistics update Add validation for compliance_level before setting it in extra_statistics to prevent potential undefined variable reference. pr_agent/algo/utils.py [399] -get_settings().set('config.extra_statistics', {'compliance_level': compliance_level}) +if 'compliance_level' in locals(): + get_settings().set('config.extra_statistics', {'compliance_level': compliance_level}) Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion prevents a potential NameError by checking if the compliance_level variable exists before using it. This is important as the variable might not be defined if the code execution doesn't reach the compliance level calculation.	7

[AdamWalkerQodo]

/analyze

[qodo-merge-pro-for-open-source]

PR Analysis 🔬

• This screen contains a list of code components that were changed in this PR.
• You can initiate specific actions for each component, by checking the relevant boxes.
• After you check a box, the action will be performed automatically by PR-Agent.
• Results will appear as a comment on the PR, typically after 30-60 seconds.

file	Changed components
utils.py	Test Docs Improve Similar   ticket_markdown_logic (function)   +84/-33
ticket_pr_compliance_check.py	Test Docs Improve Similar   extract_ticket_links_from_pr_description (function)   +6/-1

---

💡 Usage guide:

---

Using static code analysis capabilities, the analyze tool scans the PR code changes and find the code components (methods, functions, classes) that changed in the PR.

The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR:

/analyze

Language that are currently supported: Python, Java, C++, JavaScript, TypeScript, C#.
See more information about the tool in the docs.