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: to auto create Jira software tickets from JSM Incident

Richard Lim_kv643t

Hello, I tried to research about this topic but not able to find the direct answer hence I am writing to the community for some advise.

I am trying to build an automation that should auto create a Jira Software ticket once a JSM ticket has been created then linked the 2 tickets together.

I tried to build the rules below but it always fails at the creation of the Jira software ticket.

Automation rules - failed.jpg

Regards,

Richard

Accepted answers

Walter Buggenhout

Hi @Richard Lim,

It's good that you already shared a screenshot of your full automation rule, but it also helps if you could look at the rule's audit log and share the error message it shows.

There is a good chance that this is related to your automation rule's scope. Since you are working across 2 projects here, your rule will not work if it is tied to your JSM project only. The scope - which you can see on the rule details page of your automation rule must include both projects: the JSM project, but also the JSW project where you are trying to create the issue. The scope can only be changed by a Jira Administrator and by editing the rule from global automation.

If that is not the cause, do share more information about the error message you find in the rule's audit log.

Hope this helps!

All comments

Walter Buggenhout

Hi @Richard Lim,

It's good that you already shared a screenshot of your full automation rule, but it also helps if you could look at the rule's audit log and share the error message it shows.

If that is not the cause, do share more information about the error message you find in the rule's audit log.

Hope this helps!

Bill Sheboy

Hi @Richard Lim

Please post an image of the audit log details; that will provide the specifics of the error to help the community offer suggestions.

Until we see that...

The Issue Created trigger can fire so quickly that some data may not yet be available to the rule. This can cause unexpected rule behavior and errors. The work-around / fix for that is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule a bit, reloading the issue data before proceeding with the other steps.

Hi @Walter Buggenhout

FYI that project-scope rules can create (or clone) issues into other projects. However to access other projects for read (or update) requires multiple-project or global scope rules.

Kind regards,
Bill

Richard Lim_kv643t

Hello @Walter BUGGENHOUT and @Bill Sheboy ,

Appreciate on your responses. Please see attached screenshot on the audit logs, I have also added an extra step at the end to link the 2 tickets together but still failing at the step on issue creation for Jira Software.