Unable to create epic issue type via the automation

[Garret Zhang]

I've created a simple automation to basically create a epic in another project when a service desk ticket transaition to closed. Below is my automation:

However, I am getting the following error:

Create issue

Error creating issue

Given parent issue does not belong to appropriate hierarchy. (parentId)

It sounds like there is a hierarchy issue, I can't create epic from a standard issue type. Why would this be the case though? I am not trying to create an epic and link it as a child issue to the standard issue. This is simple to create an issue (in this case epic), there shouldn't be any relevant with issue hierarchy? please help!

Am I missing something else?

[Garret Zhang · Accepted solution]

@Trudy Claspill @Bill Sheboy - Thanks for the reply, I am able to get the epic created in a different project. Like Trudy said, I was trying to set epic link and parent issue, which is incorrect.

However, the newly created epic did not link back to the original service desk ticket. This is a global automation with both projects listed. 

[Bill Sheboy]

Looking at your rule image, the branch is to the issue just created: the epic.  And then you try to link that to the most recently created issue: which is also the epic.  So it tries to link to itself.

As noted earlier, please try removing the branch, as that will then link the trigger issue to the most recently created one: the epic.

[Trudy Claspill · Accepted solution]

Hello @Garret Zhang 

In your Create Issue step, what fields are you trying to set within the Epic you are creating?

From the error message it sounds like you might be trying to set the Parent field or a similarly named field.

[Bill Sheboy · Accepted solution]

Hi @Garret Zhang 

Would you please post an image of the audit log details showing the rule execution with that error?  I wonder if there is another cause of what you are seeing?

In the meantime...

What is the scope of this rule: project, global, or multiple-project?

That is relevant as all three scopes can create issues in other projects, but only global and multiple projects can edit them, and the link action would try to do that.  The scope must change for linking to happen this way.

Finally, the way your rule is constructed, it will try to link the newly created epic to itself.  If you instead wanted to link the newly created epic to the trigger issue, try removing the branch:

• trigger: issue transitioned
• condition: test the Resolution...
• action: create the new epic in the other project
• action: link issue (i.e., the trigger issue) to the most recently created issue

Kind regards,
Bill