nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation rule: Trying to re-fetch data on a scheduled "Create new task"

James Nelson

I'm trying to schedule a task creation to happen, which then fills in the summary, description, then sets an assignee and reporter. The Assignee automatically gets a notification that the ticket is created, but I want to email the "Reporter" (who is just has a "customer" license) that this ticket is created (with ticket ID, etc). But when I try to "Re-Fetch" issue data so the "send email" task has the needed info, I get this error:

The rule has been configured with components that require issues to be provided by the trigger. You need to use the option to run JQL to provide issues. The following components require issues: Re-fetch issue data

I've attached the full rule structure. What am I missing?

Accepted answers

Marcus Jones

Not sure why my replies aren't being reflected so I'll try again here. As I was thinking through this there is a better way. You'll just want to add a Branch for "Most recently created issue" after your "Create Issue" action. Then add your re-fetch issue data and send email actions within that branch.

Created Issues.png

All comments

Marcus Jones

Hi @James Nelson ,

Since you added in a "Re-fetch Issue Data", you'll need to check the box next to "Run a JQL search and execute actions for each issue in the query." Then simply add in your JQL. In the simplest form, you could just add the JQL for the project you are working in so it would look like:

Project = "Data National Programs"

James Nelson

So with that JQL you gave and making sure the "Only include issues that have changed since the last time this rule executed" box is checked, it should only effect the issue being created by this rule, right?

Marcus Jones

Apologies, as I was thinking about this a better way would be to add a branch for created issues. After your create issue action, add your branch for "Most recently created issue" and then re-fetch and send email within that branch. Apologies for any confusion!

Created Issues.png

Marcus Jones

Apologies, as I was thinking through this there is a better way. You'll just need to add a branch after your "Create Issue" action that is branched on "Most recently created issue". Then add your re-fetch issue data and send email within that branch.

Created Issues.png

Marcus Jones

Created Issues.png

James Nelson

This feels like a clunky way to do it, but it seems to be working. Thanks for the assist.

Marcus Jones

Certainly. Perhaps another community member has a better way to achieve this, but glad it is working!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management