feat(jira): add get_recent_projects tool to fetch recently viewed projects

[abesticode]

Summary

Add a new tool get_recent_projects to the Jira plugin that allows users to fetch up to 20 recently viewed Jira projects.

Changes:

• Add get_recent_projects.py: Tool to fetch up to 20 recently viewed Jira projects
• Add get_recent_projects.yaml: Tool configuration with expand and properties parameters
• Update provider/jira.yaml: Register the new tool in the provider
• Bump version from 0.0.3 to 0.0.4

This feature uses the Jira REST API endpoint /project/recent.

API Reference:

• Jira REST API v3 - Get recent projects

Related Issues or Context

Addresses user request for "Get latest updates from the Jira Projects" functionality.

This PR contains Changes to Non-Plugin

• Documentation
• Other

This PR contains Changes to Non-LLM Models Plugin

• I have Run Comprehensive Tests Relevant to My Changes

This PR contains Changes to LLM Models Plugin

• My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking)

• My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node)

• My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.)

• My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.)

• My Changes Affect Structured Output Format (JSON, XML, etc.)

• My Changes Affect Token Consumption Metrics

• My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.)

• Other Changes (Add New Models, Fix Model Parameters etc.)

Version Control (Any Changes to the Plugin Will Require Bumping the Version)

• I have Bumped Up the Version in Manifest.yaml (Top-Level Version Field, Not in Meta Section)

Dify Plugin SDK Version

• I have Ensured dify_plugin>=0.6.0 is in requirements.txt (SDK docs)

Environment Verification (If Any Code Changes)

Local Deployment Environment

• Dify Version is: , I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration.

SaaS Environment

• I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration

[gemini-code-assist]

Summary of Changes

Hello @abesticode, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a significant enhancement to the Jira plugin by adding a new get_recent_projects tool. This tool allows users to quickly access a list of their recently viewed Jira projects, directly addressing a user request for improved visibility into project updates. The change integrates seamlessly with the existing plugin structure, providing a valuable new capability for interacting with Jira data.

Highlights

• New Tool Added: A new get_recent_projects tool has been added to the Jira plugin, enabling users to retrieve a list of up to 20 recently viewed Jira projects.
• Jira API Integration: The new tool leverages the Jira REST API endpoint /project/recent to fetch project data, ensuring direct and up-to-date information.
• Tool Configuration: Configuration for the new tool, including expand and properties parameters for detailed data retrieval, has been defined in get_recent_projects.yaml.
• Plugin Registration: The jira.yaml provider file has been updated to register the newly added get_recent_projects tool, making it available within the plugin.
• Version Bump: The plugin version has been incremented from 0.0.3 to 0.0.4 in manifest.yaml to reflect the new feature addition.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a new get_recent_projects tool to the Jira plugin, allowing users to fetch recently viewed projects. The implementation is clear and adds valuable functionality. My review includes two suggestions for the new Python tool file to enhance its robustness: one for more consistent handling of empty API responses and another to improve error reporting for failed API calls. These changes will make the tool more reliable and easier to debug.