How do I link a parent issue with epic created in automation?

[ANISH TANEJA]

I am creating an epic in jira automation and i am setting some particular fields in the epic.

I am unable to find the 'Parent Link' field in the list of fields.

Do you have a solution on how can I link the epic to a particular parent (feature issue type)?

[Trudy Claspill]

Hello @ANISH TANEJA 

Welcome to the community.

You will have to do that with code since the field is not available in the list.

Can you show us the details of your automation rule? We can then point out where you need to add the code.

[ANISH TANEJA]

[ANISH TANEJA]

Am i using the correct code in the Additional fields section?
the one that you see '13074' is the parent that I want the epic to link under

[Trudy Claspill]

Do you get an error when this rule runs?

Is the parent issue key a static value that should be used in every execution of this rule?

Can you show us the entire rule - all the components of the rule?

[ANISH TANEJA]

Yes, the parent issue key is a static value in this rule. 
We will have the same parent issue key for all the epics created in the current Fiscal year and when the next fiscal year starts, we will then change the parent issue key static value to another parent issue key static value (next fiscal year parent issue)

[Trudy Claspill]

The code looks correct. Have you tried it? Is it successful?

[ANISH TANEJA]

Not tried yet, will try soon.
Thanks for the input.
What is the background understanding behind this code?
I mean I saw one of the articles and tried to copy it but is the field in the code case sensitive?

[Trudy Claspill]

Here is the reference document for advanced field setting/editing with JSON.

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

According to that document, field names are case sensitive.

[Trudy Claspill]

Ah, I gave you the wrong link. I gave you the one for Jira Cloud and your post is tagged as Jira Server.

Here is the correct page for Jira Server/Data Center:

https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html

You may need to double check the correct name for the field. Refer to this document for that:

https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html