Create issue automation fails due to unspecific mandatory field error

[Sia (Nastassia) Sharasheuskaya]

Hi all, 

I'm trying to automate the following: When an incident is downgraded to a bug with the resolution "Raised as product bug" and status Declined, two things should happen:

1. A slack message is posted (this works) 

2. A bug is automatically created and a comment is added with the link to the bug

Everything works except the creation of the bug, comment is added, slack message is posted but the bug is not created. I have added all the mandatory fields to the automation to pre-fill them and also added a screen that displays them and the user can update if needed. However, the bug is not created and the error in the logs is not specific, it just tells me that a field is mandatory but is not telling me which field 

[John Funk · Accepted solution]

Hi Sia - Welcome to the Atlassian Community!

You have the fields for the Bug being copied from the Current Issue. The Bug is the current issue, so there are no values for any of those fields. You need to copy each field from the Trigger Issue instead. 

[Bill Sheboy]

Hi @Sia (Nastassia) Sharasheuskaya -- Welcome to the Atlassian Community!

It appears there is a required field for your Bug issue type that is not set.  Please check what may be missing and include that when the issue is created.

Hi @John Funk 

I believe the "current issue" is the trigger issue for the rule shown, and not the Bug issue which has not yet been created.

Kind regards,
Bill

[John Funk]

@Bill Sheboy  Inside the creation of the Bug? I don't think I have ever seen that done. At the very least the trigger issue should work, should it not? 

[Bill Sheboy]

Yes, and...the Current Issue {{issue}} changes based on scope within the rule.  The Trigger Issue {{triggerIssue}} is constant throughout the rule (other than when changing for a scheduled trigger with JQL iteration).

For example:

• trigger: ... Trigger Issue, Issue, and Current Issue are the same
• condition: ... Trigger Issue, Issue, and Current Issue are the same
• branch: to some issues (e.g., with JQL) Trigger Issue, Issue, and Current Issue are the same
  • action inside the branch: ... Issue and Current Issue refer to the branched-to issue, and Trigger Issue remains the original one
• action after the branch: ... Trigger Issue, Issue, and Current Issue are the same

[Sia (Nastassia) Sharasheuskaya]

Thanks for the recommedations, I tied the following:

1. Created a separate automation to remove branching but doing the same configurations for Current vs Trigger issue as you see in the screens above

2. I have edited the Current issue to Tigger issue in bug fields 

All of it doesn't work and the log is not telling me WHICH field is mandatory that is missing, from my research I saw people sharing similar logs and it spelled out the field that was missing. I have tripple checked that all the mandatory fields are being set but it is still not working 

[Bill Sheboy]

Hi @Sia (Nastassia) Sharasheuskaya 

For some context, would you please post images of:

• Your complete automation rule in one image.  That may require a scrolling browser capture, with a browser extension or screen capture tool.
• Your entire audit log details for the rule execution you describe, again in one image
• Your entire issue create action in one image

Seeing those in their entirety may provide more context, as the first rule image you showed seemed to have mutually exclusive condition tests.

Thanks!

[Sia (Nastassia) Sharasheuskaya]

Hi all, I have managed to figure it out! I have set all the fields to "target issue" and moved it from the "Current issue" branch to a separate automation that has no branches. It now works!