Automation Linked Issues: You must provide one of 'inwardIssue' or 'outwardIssue'. (issuelinks)

[Kristine Daniels]

I am trying to set up automation that links new issues to an existing issue.  This seems like it should be straightforward, but I get this error:

Rule set up:

Things I have tried based on various support articles:

• ensured the rule actor has permissions to browse the project and link issues
• ensured the linked issue field is present/visible on the edit screens of both issue types being linked

I've also tried using examples for Additional Fields:

{
   "update":{
      "issuelinks":[
         {
            "add":{
               "type":{
                  "name":"Relates",
               },
               "outwardIssue":{
                  "key":"SOC2-662"
               }
            }
         }
      ]
   }
}

Appreciate any guidance!!

[Bill Sheboy · Accepted solution]

Hi @Kristine Daniels 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

Some actions in rules need an issue to be present at a specific location in the rule, and I suspect there is no issue at the point your rule tries to add the link...

Or instead the issue to which you are trying to link is in another project and the rule scope is incorrect.

Seeing the specifics of your rule and knowing its scope (i.e., single project, multiple project, or global) will confirm this.

Kind regards,
Bill

[Kristine Daniels]

Hi @Bill Sheboy , thanks for the fast response.  Rule is currently stripped down to the part I can't get to work.  Single project scope, all issues contained.  I've set myself (admin) as Actor, but same result as when I use Automation for Jira.

[Kristine Daniels]

@Bill Sheboy , this is the full audit log snipped

[Bill Sheboy]

Thanks for that information.

Rather than using the Edit Issue action, please use the Link Issues action to do so.  Then re-test and post updated images of your rule and the audit log details.

Also I note you have changed the rule actor from Automation for Jira to your own user.  Why make that change?  Sometimes that change may cause permissions errors if the user cannot perform the actions taken by the rule.

[Kristine Daniels]

Slightly different/shorter error.  Set back to Automation for Jira for actor.  I tried both single project scope and global.

[Bill Sheboy]

That is curious...

This rule appears to be global scope, and the trigger issue is in the project S0C2 (note that is a zero in the key) and you are trying to link to an issue in SOC2 (note that is an O in the name).  And so these issues are not in the same project.  Is that correct as you mentioned earlier the issues were in the same project?

What user activity / edit are you performing on the issue when the rule triggers?

[Kristine Daniels]

@Bill Sheboy , I don't think I would have EVER figured out that I had made the project code with a 0 instead of an O!    Thank you, thank you, thank you!!  I seriously thought I was losing my mind.