Automation - Clone rule failing due to priority and component(s) issues

[Mike Westcott]

I've setup an automation rule for a service desk request type to clone itself to another project upon creation.  The job has failed with the error log stating that "Component/s is required. (components), This priority is not available for this project. (priority)"

The specific service desk request type does not have these fields added, and to be expected, the automation rule does not call out for these fields to be copied in cloning.

I tried removing the component(s) field from the target project, submitting another request, and still got the same error message.  In regards to the priority, I don't want to have to mirror the priority options between project spaces.

Thanks in advance for any guidance!

[Mark Segall · Accepted solution]

Hi @Mike Westcott - 

• Component: Is component a required field in the target project config?  If so, you'll have to set something.
• Priority: I've had this same issue.  It's bittersweet that Jira Server/DC still has the ability for project-specific priority schemes.  It's great for being able to individualize projects, but terrible for automation.  You'll either have to hard set the priority on the target project to an acceptable priority and have the target team members change it or go through what you don't want to do... create mapping behavior with a nasty if smart value clause.

[Mike Westcott]

Hi @Mark Segall

Thanks for the quick response!  I hard set the priority, which solved that part of the problem.  

The screen scheme linked to the cloned issue type no longer has the component/s field added to the Create screen options, however I'm still getting an error message that it's required for cloning.

[Mark Segall]

Interesting... What about in the field configuration scheme for the target project... Is it set as required there?

[Mike Westcott]

The screen scheme that I mentioned last is for the target project.  

I had gotten the automation to go through by setting a value for the component/s field.  Other than the screen scheme, is there another place that I should be looking for where this component/s requirement is set @Mark Segall ?

[Mark Segall]

The Field Configuration scheme is the other place to look.  Field configuration is where you set whether a field is required or not vs the screen config which just establishes whether the field should show and its positioning on the screen.

[Mike Westcott]

Appreciate your help. Thanks, @Mark Segall.