Error linking issues : Issue does not exist or you do not have permission to see it.

[Fatima AALLA]

Trying this automation to link a created issue to an other it's key is in a custom field  'tested issue filled when creating issue but it doesn't work :Error linking issues : Issue does not exist or you do not have permission to see it.

[Tim C · Accepted solution]

Hi @Fatima AALLA 

A couple of things you could try ...

1) use the "refetch issue data" action to make sure that customfield value is available to the rule (as it's being run on creation - sometimes runs quicker than data changes are made).

2) try using {{issue.Tested Issue.value}}

3) try using the customfield ID instead of name ...

{{issue.customfield_xxxxx}}

4) try using the "log action" action to record the customfield value into the audit log for the automation rule - then it's easier to check what your rule is getting from the customfield and check it's a "key" value as needed for linking issues (e.g. ABC-123 format).

5) the "actor" (rules details) used to perform/run the automation rules needs to have the permission to "link issues" in your project.

I hope one of the above may help you find a solution?

[Fatima AALLA]

Hello @Tim C , thanks for replying, the rule is able to get the  tested issue key

you can see the key here, but the problem is in linking 

[Tim C]

Hi @Fatima AALLA 

Is your automation rule running under the same DSI project?

If it's linking across into a different project - then that project also needs to be added into the scope of the automation rule.

[Fatima AALLA]

Hi @Tim C , yes it's in the same project

[Tim C]

Hi @Fatima AALLA 

Is the "linked issue" field available on the edit screen used for these issue types???

[Fatima AALLA]

Hi @Tim C 

YES ALREADY

[Tim C]

Hi @Fatima AALLA 

This route works for me .... created a variable {{mykey}} holding your customfield ...

Then use this variable for the linked issue key ...

Which probably points your problem towards the timing of the rule around the creation of the issue and/or the user which is being used for running the rule (actor).

Perhaps, as a test, try changing the rule to trigger on editing of the customfield value rather than on creation and see if the automation works?  

[Fatima AALLA]

That works for me too !! thanks  @Tim C  you saved my day!

[Tim C]

@Fatima AALLA  - no problem - glad we got there (eventually).

[Alagu Murugan Krishnan]

Great! Tim C