Automation: JSM : Form

Question

I have field "Action" in form, it has respective custom field in Jira, when a specific field is selected from Action dropdown then a specific value should get selected in another custom field. I have written this rule, but it is not working. I'm having difficulties in debugging this issue.

Automation should trigger:

1) when form is submitted or edited.

2) Action = Request change of an existing zone setup/rule or WAF Exception control request

3) Product Impact= Low

The most important problem is that rule is not getting triggered for the request type on which i want it to work, it is getting triggered for request for which i didn't make any change.

Any help to debug would be appreciated.

Bill Sheboy · Answer

Hi @Neeta Dubey

Yes, and...to the suggestions from @Marc -Devoteam-

This symptom is likely related to racetrack timing problems, as the form is not attached fast enough to be available when the rule is triggered for an edit.  (This is a common problem for work item creation, form data, asset data, etc.)

Additionally, there are separate rule triggers for Form Attached and Form Submitted.  Thus, please test to confirm if the Work Item Updated trigger is sufficient for your cases.

The mitigations for the racetrack timing problem are:

* For this rule, add a Re-fetch Work Item data action immediately after the trigger.  That will slow the rule slightly, giving time for the form information to update, and then reloading the work item data.
* For all rules, do not use conditions in triggers.  This relatively new feature has lots of problems (which can be found as defects and suggestions in the public JAC  backlog).  Instead, add separate conditions after the above described re-fetch action.

Kind regards,
Bill

Marc -Devoteam- · Answer

Hi @Neeta Dubey

What does the audit log say?

Also it's netter to add conditions outside the rule trigger based on issues related to timing.

The rule you made will trigger when an update is done on any work item in the project.

Also there is no condition based on request type.

So what are your steps on the issue where the rule is not triggering?

Some pointers, did you make the rule in a specific space, is the issue you are updating in that space?

If not, it the rule scoped to multiple spaces, this scope can only be set from global automation (only an admin can set this).