Error cloning an issue from trigger

I have a rule that picks up an issue "due" in x many days and clones it to the same project. The trigger seems to be fine, but I'm receiving a non-descript error in the logs:


Error creating issue
Operation value must be a string
The source issue isn't anything too exotic. There are a number of custom fields, including short string, drop down, multi-select, checkboxes, and dates. I'm able to create and edit issues without errors. Additionally, I'm able to manually clone the issue without incident. Are there any known problems with a specific field type, or characters that could prevent the issue from being created?

1 answer

0 votes
Andreas Knecht Community Champion Nov 09, 2016

Hi Justin,

Sorry you've hit this problem.  This does sound like you may have hit a bug, but I think we'll be able to help you more effectively if you raise a support request for us, including your JIRA instance URL, an example issue key you're trying to clone, and the name of the rule you've created.  You can do so via

That way we'll be able to look into the logs from our side and we can try to replicate the problem!


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,726 views 3 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you