Exporting the JSON for Automation rules from production to the sandbox, importing them and selecting each of the 267 automations and then seeing that only 140 or so have been imported (and all disabled), and then receiving a 'An unknown error occurred. Please reload and try again." message is really terrible UI.

I do see now that there is the option to retain the owner at least, but on the sandbox I prefer to be the owner anyway.

If only admin issues would get the same treatment as the flashier front end issues then our headaches wouldnt be so bad.

Atlassian? More like Half-ass-sian. 

Everything you implement half of it, then drop the ball for 20 years until the ticket is old enough to drink. 

You only allow importing one rule at a time. Then what the heck is the point of making us select the single rule after loading the file? You have a co-op with doctors treating carpal-tunnel syndrome? 

Do you know why we have so much automation rules to import? Because your OOTB workflow post-function sucks. 

I cannot emphasize enough how important this VITAL capability is to such a tool like an "Import" functionality. It's implemented in just about every other facet of the Atlassian experience, so I would think it should be a reusable modular UI element that should just be "enabled". Approaching 2 years since this ticket was raised and still in "Gathering Interest" with no response at all in the ticket from the dev team leads me to believe it's: 

• A) Not so simple (especially if all the code is still original CodeBarrel code and was just lifted and shifted into the stack (yeah I still occasionally see Greenhopper references in source code all these years after Greenhopper became part of the Jira Software core offering, so this is very possible) 
  OR
• B) This system is essentially on the "pay-no-mind list". The linked new feature policy on the ticket is not much help as Automation is not a listed product or category

I'm in similar boat to @Jeff Gunawan in that we need this in order to be able to use your sandbox functionality effectively and this is not a viable option for Enterprise customers without having something as basic as a "Select All".

Select All has been a core function of any file select menu since the dawn of commercially-available home computers and the Graphical User Interface. Soon we'll be able to integrate Jira with Tesla's and refrigerators, but here we are in 2022 having to literally click 113 individual checkboxes when importing a global rule backup to an environment? This comes up in various other select screens in Jira Cloud as well....because javascript? Or was this truly just overlooked, not considered?

'Select all' should be available on any & every file select menu, regardless of platform/tool.

Our team plans to copy prod data into our sandbox once a quarter. It would be ideal if we could import all the rules during this process too. Are there any updates for this request? Thanks!