HumationHuman + Automation
Back to Catalog

Auto-resolve Jira tickets with GitHub Copilot using Port Context

Port IOPort IO
297 views
2/3/2026
PostgreSQLEmailReportDatabaseCSV
Official Page

Auto-resolve Jira tickets with coding agents

Coding agents can significantly speed up development, but crucial engineering context often gets lost in the process. This guide demonstrates how to use Port as a context lake in n8n workflows to automatically generate GitHub issues from Jira tickets with rich organizational context, ensuring that important information is preserved when assigning them to GitHub Copilot and linking pull requests back to Jira. This setup helps establish a seamless ticket-to-PR workflow, bridging the gap between Jira and GitHub while leveraging Port's comprehensive software catalog as a source of truth.

How it works

The n8n workflow orchestrates the following steps:

  • Jira trigger — The workflow listens for Jira issue updates via webhook.
  • Condition check — Verifies that the issue status is "In Progress" and has the required label (e.g., "product_approved") without the "copilot_assigned" label.
  • Port context extraction — Uses Port's n8n node to query your software catalog for relevant context about services, repositories, teams, dependencies, and documentation related to the Jira issue.
  • Parse response — Retrieves the AI-generated GitHub issue title and body from Port.
  • Create GitHub issue — Creates a new GitHub issue with the enriched context from Port.
  • Assign to Copilot — Adds a comment to the GitHub issue instructing Copilot to take ownership.
  • Add issue link to Jira ticket — Adds a comment to the Jira ticket with the GitHub issue URL, providing clear traceability.
  • Mark ticket as assigned — Updates the Jira ticket to add the "copilot_assigned" label, preventing duplicate processing.

Setup

  • [ ] Connect your Jira Cloud account and enable issue_updated events
  • [ ] Register for free on Port.io
  • [ ] Connect your Port.io account and add the API key
  • [ ] Connect your GitHub account and select the target repository
  • [ ] Ensure a Copilot bot or @copilot user has access to the repository
  • [ ] Confirm the workflow webhook or Jira trigger URL is active
  • [ ] Test by moving a product_approved ticket to In Progress.
  • [ ] You should be good to go!

Prerequisites

  • You have a Port account and have completed the onboarding process.
  • Port's GitHub app is installed in your account.
  • Port's Jira integration is installed in your account.
  • You have a working n8n instance (Cloud or self-hosted) with Port's n8n custom node installed.
  • Your GitHub organization has GitHub Copilot enabled, so Copilot can be automatically assigned to any issues created through this guide.

⚠️ This template is intended for Self-Hosted instances only.

Jira to GitHub Issue Auto-Resolution Workflow

This n8n workflow demonstrates a basic setup for integrating Jira and GitHub, specifically focusing on triggering actions based on Jira events. While the provided JSON defines the initial nodes, it lays the groundwork for a powerful automation that could, for example, auto-resolve Jira tickets based on GitHub Copilot suggestions or other GitHub activities.

What it does

This workflow currently sets up the foundational components for a Jira-GitHub integration:

  1. Listens for Jira Events: The workflow is triggered by events occurring within Jira. This could be anything from a new ticket being created, a status change, or a comment being added.
  2. Conditional Logic (Placeholder): An "If" node is included, ready to implement conditional logic. This allows the workflow to proceed only if certain criteria are met (e.g., a specific issue type, status, or keyword in the description).
  3. Interacts with Jira (Placeholder): A Jira Software node is present, indicating the capability to perform actions back in Jira, such as updating a ticket's status, adding comments, or assigning it.
  4. Interacts with GitHub (Placeholder): A GitHub node is included, enabling interactions with GitHub repositories. This could involve creating issues, commenting on pull requests, or fetching repository information.
  5. Documentation/Comments: A sticky note is included, likely for internal documentation or to provide context within the workflow canvas.

Prerequisites/Requirements

To fully utilize and expand this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Jira Account: Access to a Jira instance with appropriate API permissions.
  • GitHub Account: Access to a GitHub account with appropriate API permissions.
  • Jira Credentials: Configured Jira API credentials within n8n.
  • GitHub Credentials: Configured GitHub API credentials within n8n.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button (usually a cloud icon with an arrow pointing down) and paste the JSON.
    • Click "Import".
  2. Configure Credentials:
    • Click on the "Jira Trigger" node and configure your Jira API credentials.
    • Click on the "Jira Software" node and configure your Jira API credentials.
    • Click on the "GitHub" node and configure your GitHub API credentials.
  3. Define Jira Trigger:
    • In the "Jira Trigger" node, specify the type of Jira events you want to listen for (e.g., "Issue Updated", "Issue Created").
    • You might need to set up a webhook in Jira that points to the webhook URL provided by the n8n "Jira Trigger" node.
  4. Implement Logic:
    • Flesh out the "If" node with your desired conditions. For example, you might check if a Jira issue's summary contains "Copilot" or if its status changes to "Ready for Review".
  5. Define Actions:
    • Configure the "Jira Software" node to perform specific actions based on the "If" node's output (e.g., transition the Jira issue to "Resolved", add a comment).
    • Configure the "GitHub" node to interact with GitHub (e.g., create a new issue, update an existing one, or fetch information).
  6. Activate the Workflow:
    • Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.

This workflow serves as an excellent starting point for automating various development and issue management tasks between Jira and GitHub.

Related Templates

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp

This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑‍💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️‍♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business

ShadrackBy Shadrack
331

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353