Automation error related to "Linked issues" field

[Andrew Grossman]

Hello! I'm receiving an automation error related to a rule I have. This rule creates a follow-up ticket after another ticket is marked as complete, based upon if a field is filled in. The audit log is indicating that a field might not be available on the target ticket, but that seems incorrect to me. It looks like the failure is related to linking the ticket to the trigger issue. I am able to manually link issues after the target ticket is created in the web interface, so perhaps linking issues needs to be implemented differently?

Audit log error information:

Automation rule step:

Verification that there is only the one "Linked issues" field and nothing obsolete

[Eden Eliyahu]

I just had the same problem. The field should be added to the create screen.
The problem will be solved.

[Carson Holmes]

@Andrew Grossman I'm hitting the same issue.  Did you figure this one out?  Thanks.

[Frédérique Cusson]

Hi @Andrew Grossman and @Carson Holmes I have the same problem as you. I tried to add a link issue with a smart value and by selecting last created issue but both don't work. Did you find a solution?

[Bill Sheboy]

Hi @Andrew Grossman 

From your question description, I wonder: did you try to remove the set of Linked Issues field to confirm that is the cause, and not an error message...well, error?

I took a quick look and could not find this symptom on any open bugs in the Jira Cloud, Automation, or Code Barrel backlogs.

Next things to check:

• When I have seen that error before, it was because of a duplicate field name (which you ruled out) or the field was not on the add/edit view.  That seems unlikely as you noted being able to manually link the issues.
• I have seen other posts indicating occasional problems selecting the Create Issue action with the "Same project" option if this is a global/multi-project scope rule.  Perhaps try explicitly selecting the project name from the list.
• Lastly, I wonder if there is some weird timing issue with issue create and linking.  One way to test that would be to remove the linking with the create and add a branch afterwards on Most recently created issue to perform the link.

Kind regards,
Bill