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; } } }

Field value change trigger not working for created issues

Kelly Wehbi

We have an Automation created to pull data from an external source and update a field in JSM, and are currently using the "Field value changed" trigger. Everything works just fine when the value is changed in an issue that already exists, but it won't run properly when a new issue is created. We have "For: All issue operations" set, so it's not limited to specific actions. I don't understand what the "Create issue" operation is for if it doesn't consider a value going from NULL to something as a "field change." Any idea how to deal with this, other than duplicating the rule to have one for issue creation and one for issue updates?

Thanks!

Accepted answers

All comments

Mark Segall

Hi @Kelly Wehbi

Is the issue being created via the portal or is it created from another automation? If the latter, you'll need to make sure the Allow Rule Trigger checkbox is set on the Rule Details.

If the issues are in fact coming in through the portal, can you please advise as to whether the rule triggers at all when an issue is created (any new entries in the audit log)?

Kelly Wehbi

@Mark Segall It’s on the portal. The logs show it was run, but there’s condition to check when it runs. It comes back as false when the issue is created, but true when it’s an edit.

Mark Segall

Can you please share a screenshot of the rule? It's a good sign that it is at least triggering.

Kelly Wehbi

@Mark Segall Had to share a GIF cause it's pretty long. Can also confirm the POST requests are working just fine.

Michał

I hit same situation on Jira Software Data center,

it should work according to documentation: Jira automation triggers | Automation for Jira Cloud and Data Center | Atlassian Documentation

but it does not, my only workaround is to create another rule with 'create issue' trigger .

Pauline Hennau

Hello,

this question is quite old but if the answer future user who encounter this bug :

I added all the operations instead of leaving the field blank "all operations" like this and it triggers perfectly at creation

Michał

thanks :-)

MHB

This worked for me in JSM DC. Thank you. Prevented an overly complicated fix. You're my hero today.

For background: "Create issue" was working when the issue was created via portal or create console, but was not working when Automation created the issue. (The "Allow Rule" box was also checked.)

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