Hello,
I do not want to set the field in the "create issue" action at 2 because it requires the "Linked issue" field to be in the "create" screen, which I don't want to pollute for users.
Using the "edit issue" action, the "trigger issue" is now referencing the newly created issue which is wrong (and returns an error).
Therefore, I have tried using the raw JSON input to update it like that, but it does not work:
```json
{ "fields": { "Linked Issues": { "is related to": "{{triggerIssueId}}" } } }
```
Here is a screenshot of the rule if this can clarify the context:
Hi Ilia - Welcome to the Atlassian Community!
Instead of doing an Edit Issue for the linked issue field, just do an action for Link issues.
Hello John,
Thank you for the suggestion, but I tried the following and it looks like the action for Link issues did not perform anything.
It did not log an error as when I did it through the Edit issue action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alright, I made it work by using the "most recently created issue" option:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.