Google Gemini Chat Model and Jira Software integration

What it does Automates code review by listening for a comment trigger on GitLab merge requests, summarising the diff, and using an LLM to post constructive, line‑specific feedback. If a JIRA ticket ID is found in the MR description, the ticket’s summary is used to inform the AI review. Use cases Quickly obtain high‑quality feedback on MRs without waiting for peers. Highlight logic, security or performance issues that might slip through cursory reviews. Incorporate project context by pulling in related JIRA ticket summaries. Good to know Triggered by commenting ai-review on a merge request. The LLM returns only high‑value findings; if nothing critical is detected, the workflow posts an “all clear” message. You can swap out the LLM (Gemini, OpenAI, etc.) or adjust the prompt to fit your team’s guidelines. AI usage may incur costs or be geo‑restricted depending on your provider n8n.io. How it works Webhook listener:** A Webhook node captures GitLab note events and filters for the trigger phrase. Fetch & parse:** The workflow retrieves MR details and diffs, splitting each change into “original” and “new” code blocks. Optional JIRA context:** If your MR description includes a JIRA key (e.g., PROJ-123), the workflow fetches the ticket (and parent ticket for subtasks) and composes a brief context summary. LLM review:** The parsed diff and optional context are sent to an LLM with instructions to identify logic, security or performance issues and suggest improvements. Post results:** Inline comments are posted back to the MR at the appropriate file/line positions; if no issues are found, a single “all clear” note is posted. How to use Import the template JSON and open the Webhook node. Replace the REPLACE_WITH_UNIQUE_PATH placeholder with your desired path and configure a GitLab project webhook to send MR comments to that URL. Select your LLM credentials in the Gemini (or other LLM) node, and optionally add JIRA credentials in the JIRA nodes. Activate the workflow and comment ai-review on any merge request to test it. For each review, the workflow posts status updates (“AI review initiated…”) and final comments. Requirements A GitLab project with a generate Personal Access Token (PAT) stored as an environment variable (GITLAB_TOKEN). LLM credentials (e.g., Google Gemini) and optional JIRA credentials. Customising this workflow Change the trigger phrase in the Trigger Phrase Filter node. Modify the LLM prompt to focus on different aspects (e.g., style, documentation). Filter out certain file types or directories before sending diffs to the LLM. Integrate other services (Slack, email) to notify teams when reviews are complete.

This n8n template from Intuz provides a complete and automated solution for creating and distributing sophisticated release notes. It connects to GitHub and JIRA to gather data from recent commits and completed tickets, using specific keywords or labels to identify key features for inclusion. This information is then processed by Google Gemini to automatically generate well-written, human-like release notes, which are then distributed via email to stakeholders, creating a complete, end-to-end communication pipeline for every new software release. This template is perfect for development teams looking to streamline their release process, ensure consistent communication, and eliminate the manual effort of writing release notes. How to use Set up Credentials: GitHub JIRA (Software Cloud API) Google Gemini (or another PaLM/LLM provider) Your SMTP email server. Configure the GitHub Trigger: Select the Github Trigger node. In the Repository Owner field, enter your GitHub username or organization name. In the Repository Name field, select the repository you want to monitor. Verify the JIRA Integration: Important:** This workflow assumes your commit messages contain a JIRA key (e.g., "PROJ-123: Fix login bug"). Select the first Code node. It uses a regular expression ([A-Z]+-\\d+)/i to find JIRA keys. Adjust this expression if your team uses a different format. Select the Get an issue node and ensure your JIRA credentials are correctly configured. Customize the AI Prompt: Select the Basic LLM Chain node. You can edit the prompt to change the tone, style, or structure of the generated HTML release note to match your company's standards. Configure Email Notifications: Select the Send email node. Update the To Email field with the recipient's email address (e.g., a team distribution list or a stakeholder's email). Customize the From Email and Subject line as needed. Activate Workflow: Save your changes and activate the workflow. Now, every push to your configured repository will trigger the automated generation and sending of release notes. Required Tools GitHub: To trigger the workflow on code pushes. JIRA: To fetch details about the tasks and bugs included in the release. Google Gemini: To intelligently generate the release note content. (You can swap this for another LLM supported by n8n). SMTP Provider: To send the final release note via email. Connect with us Website: https://www.intuz.com/n8n-workflow-automation-templates Email: [email protected] LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Worflow Automation Click here- Get Started