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)
That's not javascript (js), that's groovy, as such it needs to have the extension .groovy.
The exception shows you that the wrong interpreter is being invoked:
sun.org.mozilla.javascript.internal.EvaluatorException
If you have applied the updated workflow with the script post-function, there will be an exception in the logs.
worked like a charm. it's always the simple things that end up consuming far too much time. ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think this is a different problem, please ask a new question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Consider it confirmed. I decided it use an absolute path since $CATALINA_BASE looked not to be set. That path is D:\JIRA\work\Catalina\lockedestimate.js where D:\JIRA is the path for our JIRA install.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tanner,
Could you confirm that you have checked the notes from Jamie here?
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.