Error which doesn't enable cloning an issue

[Eitan Gur]

"com.atlassian.jira.exception.createexception: Error occurred while creating issue through workflow"

message appears - no indication why. Any info? Directions to investigate?

will be appreciated.

Thanks

[Marcos Sanchez · Accepted solution]

Hi,

Do you have any condition or validation in your create transition?

It may be one of the things to check.

Regards,
Marcos

[Eitan Gur]

Thanks.

Checked - nope.

[Marcos Sanchez]

Do you have access to logs? 

Maybe it could have more information about your error.


Regards,
Marcos

[Eitan Gur]

Yes I checked the logs as well - it wasn't so indicative.

However now I could reach the correct workflow of the issue and the first direction you proposed was correct - create issue status in the workflow included validator which condition wasn't fulfilled for the clone operation.

Once I aligned the issue to fulfill these conditions the clone was successful.

@Marcos Sanchez thank you for your help! 

[Marcos Sanchez]

It's great to hear that!

Have a nice day,
Marcos.

[Liam Maeder]

Good Day

I also had this problem but found that there was a validator, who's error message was not passing through correctly, on the create step. After making sure the required field was populated, it all worked perfectly.

I thought I wwould share this in case any one else is experiencing the same issue.

Warm Regard
Liam

[Rashmi BM]

Hi @Liam Maeder  & @Warren Kent 

What was the field that needed update in the issue going to be cloned. Kindly suggest.

Thanks,

Rashmi.

[Warren Kent]

Hey Rashmi,

I cant recall the exact field - it might have been a custom or system field. i would suggest checking the issue's workflow (specifically the create flow) and see if you have any validation in place for specific fields and check to see that those fields all have a value. If not, then put something in and see if this resolves your cloning issue.

[Warren Kent]

We introduced a validation on our project's workflow on the create transition. We then tried cloning a ticket that was created before the new validation was enforced on the workflow and ended up getting the error. The resolution here was to populated the field with a value on the "older ticket" and you would then be able to clone the ticket accordingly.