Create a Jira ticket monitoring system with Zapier Agents

I'm going to show you how to create an incomplete Jira Tickets commenter Agent in Zapier Agents, and we're going to use this incomplete Jira Tickets commenter template. Go ahead and read about how it works.

We're going to be connecting to Jira with this capability here, this specific tool that the agent's going to use, but we're going to go through all of it. So let's go ahead and get started by clicking Use Template.

There's nothing you can do on this screen besides move forward, but it is an opportunity to review first of all the agent's instructions, which are verbatim shared here. This is again that tool that it's going to use. And the trigger is going to be when there's a new issue in Jira Software Cloud. The last thing that I'll mention here is this is an official Zapier template. You can tell by the little check mark and the word Zapier. So let's click Use this template to go to the next step.

The last thing that you will do before being able to interact with the agent is connecting any relevant apps for the template. In this case, it's going to be a connection to Jira Software Cloud and it will ask you for your Jira Cloud Suite URL in addition to connecting the app. I already have mine configured, so I can go ahead and click that. But if you needed to connect a new account or manage your accounts, you can do that by clicking this widget here. Let's go ahead and click Create.

And one more note is that you can connect additional apps later. You could even change out your Jira connection to another account if you needed to. This won't be your only opportunity to do that. Let's click Create.

All right, so now we're actually interacting with the agent, and you can see how the agent works by running through these instructions. So let's do that really quick. You're an automation agent responsible for monitoring tasks in a project management system and leave comments when certain criteria are not met.

And so there's two things that's going to happen here. One is that it's going to check task fields. It's specifically looking for the field size and Sprint and making sure that they're empty, but also confirming that it's not a to do task that's in progress already. It's only looking for tasks that are part of an active workflow. You could customize this if you have different fields that you want to use or different work states that you want to use different project management states. But for now, we're going to leave those. And then finally, the end result of this workflow is that it's going to leave a comment with a mention to fill out all the missing details. And it's using this tool, JIRA Software Cloud Add Comment to issue.

So, a couple things here before we test the agent. First of all is if you wanted to change around tools, if you wanted to use a different tool, say maybe there's a different project management system that you use, you could go to insert tools and add tools from any of the 7,000 plus connected apps that Zapier works with. But we're going to leave it as is to demonstrate how this template works.

And last detail is this trigger here is set to look for these new issues that meet the criteria we discussed. But there are other triggers that you could potentially use. If you wanted to customize this, you could click on the trigger itself, this widget icon, and then replace the trigger to see the other options. But again, we're not going to change this because I want you to understand how this template works. And so without further ado, we can test this agent.

Actually, there is one more thing, and that's whenever you use a trigger that's not set to on demand, in order to use this agent outside of this workflow, you need to click to enable the agent. So I might as well do that now, even though we're running the tests, so, so that I don't forget after running the test, to show you how the agent works outside of the testing mode. All right, so let's click Test Agent and see if it finds something that matches these conditions.

And this agent preview you're seeing here is going to work very similar to the agent again once it's set up and ready to go. Okay, so as you can see, it's running that trigger. You can click to expand if you're curious about what's happening in the back end by clicking on this little carrot and then unclicking it. So as you can see, it did find a task. It says the required fields for this task are missing and the status is not set to to do. You can kind of follow the logic here. It says I will leave a comment on the JIRA issue to remind the assignee to fill out all the missing details.

And okay, so this is for BBC1, because I'm going to show you in JIRA where it makes this comment. We are going to click approve and we only need to do that when we're testing the agent. We don't have to click approve once the agent's actually running. All right, so it's going through. It went through the action. It's already complete.

You can kind of see again that logic if you want to click here, but let's go ahead and look. So it's BBC one in Jira, and here's my little JIRA board of tasks. And it looks like BBC1 is right here. And as you can see, it successfully added the comment and it works.

So now that we know that our agent works, let's go ahead and flip it over to the live version. As a reminder, this agent is set to run with the trigger that works based on actions that happen in Jira outside of Zapier, and so you won't be able to interact with the agent in terms of a back and forth chat conversation. If it was set as a trigger to On Demand, on this screen, instead of seeing New chat, you would just see the words run in a button, but just so that you can see kind of what it would look like.

If you click New chat, it'll bring up the working agent. We're outside of test mode at this point, but again, because this agent is using a different trigger than On Demand, there's not really much I can do here. So at this point, you are ready to use the incomplete JIRA tickets commenter. I can't wait to see what you do with it.