I am building an automation to clone a ticket to a different project based on a change to a custom field and am receiving the following error:
Clone issue:
I am also seeing an issue and additional automation, and I am now wondering if this is a bug. The other automation is triggered on a change to a custom field and, if it meets the criteria, is transitioned to a new status. When it runs, I receive the following error:
Hi @Ashleigh Hamilton ,
it looks like the issue type in the destination project doesn't exist or misses some fields that you define e. g. PIR Status.
Could you please check that?
As @Mike Maurer mentioned, might be worth setting the issue type to Idea - even if this automation is cloning an idea from one JPD project to another JPD project:
If there error persists after that adjustment, let us know.
PIR Status is a field in the destination project. I removed all the custom fields from that step and I still get the same error.
Hi @Ashleigh Hamilton
Yes, and...to the other suggestions provided:
What is the type of your project: company-managed or team-managed? You may find this information in the project list or at the bottom of the left-side page expanding area.
This is important because the issue types and custom fields used by team-managed projects are usually unique to each project. And JPD is built upon a team-managed project approach.
The workaround for these differences is to specifically select the issue type when creating / cloning an issue. And when necessary, use JSON edit to set the custom field values using their IDs rather than field names (or smart values).
Kind regards,Bill
OK, thanks for checking.
Are both project projects Jira Discovery Projects (JPD)?
If yes, are the custom fields JPD custom fields or global custom fields?
With global custom fields you can use the custom field IDs to control the fields.
@Ashleigh Hamilton ,
Could be an issue with the Actor (Automation for Jira), and this user not having JPD permissions. This has been an issue for some customers in the past, and a known minor bug engineering is aware of.
Try switching the Actor to someone who has JPD permissions, and retesting to see if there are any different results / errors.
If you're encountering errors while attempting to clone or create issues using Jira automation, our app Deep Clone for Jira, could significantly streamline your process. With Deep Clone, you can reliably clone issues across projects, including all fields, attachments, and issue types, while bypassing common automation hurdles.
It looks like you're new here. Sign in or register to get started.
