This is a must have otherwise the application admins need to maintain all the SD's automations (related to issue updates) which requires more effort and a higher time to implementation.

use plugins therefore "Automation for Jira" or "Scriptrunner"

Like so often, this should not be a feature that is beeing considered, this is a bug because the "feature" itself should have been available from the beginning on.

It shouldn't be that complicated to implement this. I don't like to use third party add-ons for everything just because Atlassian is doing things halfway.

This feature would enable priority calculation after issue has been created: https://confluence.atlassian.com/servicedeskcloud/calculating-priority-automatically-827107708.html

This is usefull if customer should not set urgency and impact.

We have the same case as Urs Friedli. Unfortunately, this 3rd step is often forgotten by our agents and the consequences for the customers are momentous. They cannot view their tickets anymore. So I want to cover this serious case by creating an automation which is not possible right now!

Another Use Case:

1. Customer creates a request of request type A and issue type A
2. Agent moves the issue from type A to type B
3. The request type must now automatically be changed from request type A to request type B

If this is not done, the request does show up with the wrong, old request type inside the portal for the customer. This can also be worked around with the JIRA Automation Plugin (with an "Issue updated" trigger).

An alternative Workaround is to use the "Status changed" trigger if the issue does change the workflow status when being moved from issue type a to issue type B.

This feature would be great as the editing of information wouldn't always happen (or could change) if adding a formal triage step.

Automating the workflow based on an edit would be a great addition to the service desk automation options.