Automation Rule fails due to status being a non editable status

[Jeffrey Bistrong]

I have an automation rule that is failing due to the ticket not being editable. Trying to figure out how I can add an exception to this status properties that would allow the automation rule to make the edits it needs to

[Charly [DEISER] · Accepted solution]

Hi @zaharovvv_suek_ru

Yes, When you are creating the components you can select the assignee from the same options.

In this case i'm creating the component named "Test", Carlos Aparicio is the Lead and in the last option i'm selecting that default assignee is the Lead of the component.

Hope this helps!

[zaharovvv_suek_ru]

Thanks, Carlos, for your reply! 

It works fine when component is created, however I would like to set assignee of issue based on component lead. That is Assignee of issue should be lead of selected component.

the component.

[Nic Brough -Adaptavist-]

That is what Carlos posted - you set the assignee to the component lead (and drop the field off the create screen if you don't want the users to override the "automatic" option)

[zaharovvv_suek_ru]

Thank you very much!:) 

[incadea - Admin Jira]

Nice, but how can I steer the automated assignment when component is changed or added at a later stage on ticket processing?

I mean the ticket is unassigned and then some dispatcher selects a component. It should then automatically assign it to the component lead if setup, right?

Please advise

thank you