Automation rule for cloning ticket into a different project with required field

[James Wardle]

Hi

I'd like an automation rule in place to be able to clone a ticket into a different project, but that project has a required field (Components) that isn't required in the original project.

Is there a possible solution to this? In theory it should be that when the cloned ticket is moved, it also sets a value in the Components field, but I can't work out a way to do that.

This is what I currently have.

Thanks!

[John Funk]

Hi James,

Inside the Clone issue action, click the Choose Fields to Set dropdown and select the Component field. Then you can set a value for it. 

[James Wardle]

Hey @John Funk

Thanks for the reply. When I set the value for Components, I'm presented with the Components for the current project and not destination project (which differ).

Is there a way round that?

[John Funk]

Not if you are using Clone issue. You should use the Create issue instead and then list all of the fields in the new project, assuming there are not too many of them to mess with.