Imagine getting a recipe that just says “add ingredients and cook.” Technically, it’s a recipe, but good luck making dinner with that level of detail.
It’s the same with your development team. They need tickets with complete information to estimate work and move projects forward. Without them, they’ll be stuck playing detective, trying to figure out what needs to get done.
Keep your projects moving forward quickly by having AI chase down those details—not your development team. With Zapier Agents, you can build an AI agent that monitors new Jira tickets, checks for incomplete essential fields, and automatically posts friendly reminders right on the ticket. No more chasing down teammates or discovering half-empty tickets days later.
Watch the video below to see how it works, or keep reading for step-by-step instructions.
Read the video transcript
How to set up an incomplete Jira ticket monitoring system with Zapier Agents
In this example, we’ll start with a template in Zapier Agents. This template enables the agent to monitor Jira tickets, checking whether essential planning fields (like size and sprint assignments) are filled out. When the agent finds missing information, it posts a comment to remind users directly on the ticket.
Note: By default, the agent’s instructions are to check tickets that have moved beyond the to-do status and verify whether the sprint or size fields are empty. But you can easily customize the template to check for the status and fields that help move your projects forward.
To get started, click on the button below, then follow the steps to customize your agent.
Zapier is the most connected AI orchestration platform—integrating with thousands of apps from partners like Google, Salesforce, and Microsoft. Use interfaces, data tables, and logic to build secure, automated, AI-powered systems for your business-critical workflows across your organization’s technology stack. Learn more.
Step 1: Activate your template
Step 2: Connect your Jira instance
-
After going through a summary of what the template does, you’ll need to sign in to a Jira Software Cloud account to connect your apps. Click Connect to use a previously connected account or connect a new account.
-
If you’re connecting for the first time, the system will prompt you to log in based on your Jira version. To connect your Jira Software Cloud account, enter the URL of your Jira Cloud Site (e.g., yoursite.atlassian.net).
Step 3: Customize the agent’s instructions
The trigger is set to Jira Software Cloud: New issue by default, which monitors for newly created tickets in your connected Jira instance.
The template is ready to use without further changes, but you can customize the instructions to make it more useful to your existing workflow, if you’d like.
You can change the following:
-
Field requirements: By default, the agent checks for the size and sprint fields. If these fields don’t exist in your Jira setup, you’ll need to create them through Jira’s Manage Fields section, or edit the instructions to check for different field names.
-
Status filtering: The agent only flags tickets that are not in to-do status, meaning it ignores early-stage planning tickets and focuses on active work items. You can easily change that to fit your process.
-
Comment template: The default comment reads: “Hi [Assignee Name], please fill out all missing details for this task, including the [field names], thank you.” You can customize this message, add additional users to tag, or modify the tone to fit your company style.
Step 4: Test and deploy your agent
-
To start, create a sample Jira ticket, move it out of the to-do status, and leave the size and sprint fields empty. If you customized the Instructions, make sure the sample ticket matches your chosen fields and status.
-
Click Test agent to run a sample workflow. The agent will check your existing Jira tickets and identify any that meet your criteria (in this case, not in to-do status and missing the size and sprint fields).
Note: The agent may need approval to post comments during testing—click Approve when prompted.
Unlike agents that use the On demand trigger, this one requires you to manually turn it on. Look for the Enable agent toggle and turn it on when you’re done testing and ready to use your agent.
Take your project management systems to the next level with Zapier Agents
Zapier Agents provide flexible customization capabilities to suit your dev team’s unique needs. And this template is just the start of what you can do. Customize your agent to add team notifications, create escalation workflows for incomplete tickets that fall within a specific time period, or adapt the logic for other project management systems beyond Jira.
Explore our guide to getting started with Zapier Agents for more templates and ideas.