Like other things which are missing: this is a no brainer to add.
Sorry if I might come accross rude but sometimes I really feel whoever is testing Jira should develope a new way of doing so...

This would be a very useful feature - we have > 10 teams in our newly-launched Product (and counting), and automation is key to maintaining a degree of standardization in our development processes. Re-deploying all of the automation rules to each project is time-consuming, error-prone, and stifles change, because of the amount of work involved every time an update is needed. The Automation feature is powerful today, but could be so much better.

I am very interested in this.  I just created a new Jira project, and having to enter all the rules from my other project into this one, is going to be a time consuming, manual process.

@here Does this ticket have a Jira CLOUD equivalent ticket that I can upvote with the future of Jira Server being what it is? Any tickets in the Jira Server related customer requests projects are fairly moot I would think in terms of trying to get anything done.

We are close to rolling out automation company-wide, but this feature is holding us back. numerous product owners are managing multiple projects. To encourage self-service, they should either be able to assign multiple project leads to the projects they are responsible for, or be able to import rules. Please bring this feature to development soon! 

This would be very useful you can export the rule, as Project Admin, but then you depend on Jira Admin to import a given rule on another project you are the Project Admin.