Possible Bug: Automation Failing to Clone or Create Issue on a Different Project

[Ashleigh Hamilton]

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:

Failed to fetch fields for project/issue type -

I then changed the automation to create an issue, but received this error: 

Create issue: 

Error retrieving the issue type fields for project/typeId -

10188/10370

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: 

TRANSITION ISSUE

No transitions were performed by this user.

PI-1142

My workflow is set up to allow the status of the ticket I am testing to move from its current status to TNT DONE.

[Nick Haller · Accepted solution]

Hi @Ashleigh Hamilton ,

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.

[Mike Maurer · Accepted solution]

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?

[Ashleigh Hamilton]

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. 

[Mike Maurer]

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.

[Nick Haller]

@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.

[Ashleigh Hamilton]

So the fix ended up being a mix of setting the Issue Type to Idea and changing the Actor from Jira Automation to myself.

When I just changed the Issue Type, I received an error saying, "Could not find issue types for project," which made no sense because the destination project is also a JPD project. But when I also changed the Actor, the error was removed. 

I then tested just changing the Actor, and the automation failed to create the ticket, confirming that it was a mix of the two actions to resolve the issue.  

Interestingly enough, for the second automation that I shared, where my issue was not transitioning to a new status, changing the Actor fixed the issue. So, it definitely seems to be a bug. 

[Bill Sheboy]

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

[Luka Hummel - codefortynine]

Hi @Ashleigh Hamilton

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.