Component id is not valid

[Nikola Perisic]

Hi community.

Here's the situation: I have created an automation to clone the issue from a service management project. This automation also copies the Priority, Repository (custom field), Attachment and Components from service management to software project. Service management project contains the components, where the software project doesn't contain any components. When a user creates the request from jira directly (not the customer portal, rather the agent view), it gets linked with no issues.

The problem occurs only when the request has been raised from the customer portal. What could be the issue here? The Components field is also present on the screen for both service management and software projects.  

The automation rule shows error in logs: Component (id here) is not valid. Even though this component exists (checked this with the API call).

[Luka Hummel - codefortynine]

Hi @Nikola Perisic

If you are willing to use a third-party app, you could try our Deep Clone for Jira.

Deep Clone can create missing Jira components in the target project.

[Melo]

Hi @Nikola Perisic, I am a bit confused, Isn't it the expected behaviour. When setting up an automation rule to clone issues from JSM to a Jira Software project, and the target project does not have components configured, you might encounter issues if the automation attempts to copy components that do not exist in the target project.

Cheers,

Melo