That doesn't fix the horrible UX, sluggishness, confusing options, forms that present a lot of useless fields but don't give you the option to present other, more useful ones, ... I could go on.
Jira is a terrible tool.
The UX on modern JIRA has been fine for years, and the options and forms are easy to use. Granted, you can add useless restrictions and weird field configurations, but if someone configures it until it's broken, that would be on them, not really on the product.
Small companies where only a small(er) unit of people use Jira (cloud) is fine, large teams, large workflows, selfhosted or cloud: doesn’t matter. It was always terrible.
We actively discriminate against Jira in our company at the moment, and for us it works pretty good. But that is because it is not essential and we do not lean into it.
We do have all product owners meet up at least once each month and the project collaboration methods are often on the agenda to make sure we don't end up with too many different workflows that are essentially duplicates of each other. Besides the workflows (mostly oriented around kanban boards and backlogs) we just make sure that collaboration across teams use compatible workflows and epics so you don't have to copy-paste information and instead just share stuff.
Each individual team is no larger than 8 people, most are smaller.