How can I add the trigger issue as my parent for issues created from automation?

[Andy Ades]

I'm using a next-gen project with Automation for Jira (cloud). I have a rule setup for whenever an epic is created to trigger creation of new issues (not sub-tasks) with certain fields set. I'm trying to set the trigger issue as the Epic of the newly created issues, but since "parent" isn't available until an Epic is linked to an issue, I'm unable to figure out how to properly do this. Is this possible in next-gen?

My advanced code block is:

{
"fields": {
"parent": "{{triggerIssue.key}}"
}
}

The error I get in the audit logs is:

Error creating issue: data was not an object (parent)

[Michelle Larson]

Can I ask you for the code you sued to change the name on the create and edit screen?

[Dieter]

If you already know how to change the DOM tree write a speakeasy extension. You just need to reference to your JS resource in a scoped-web-reource element described in atlassian-plugin.xml There are examples at https://developer.atlassian.com/display/SPEAK/Speakeasy+Extension+Examples Scoped-web-resource also works in a classical v2 plugin that could be the other choice. You could also pack the other JS code from your field descriptions into this plugin and thus improve maintainability a lot

[Nic Brough -Adaptavist-]

Jira does not support putting a field on screen more than once, which is correct for data entry fields because you should never give a human two entry boxes for the same data item - field entry should be unique.

Could you give us a bit more detail on what you are trying to do, why, and what's going wrong? Screenshots would be handy!