Really? Was it easy enough to define mappings between all the various fields/ticket types etc? I guess you could do it per-team across an organisation.
It always seems hard enough to get information out of JIRA using JIRA when I watch our PO in planning meetings.
Yup, there was some mess around inexact mapping so we had our own conflict resolution and definition of what and how to interpret respective fields.
Honestly, JIRA easily has one of the most sluggish and horrid developer experience so the bar wasn't too high to begin with. Visual Studio Online / Azure DevOps is far better than JIRA ecosystem imo.
It always seems hard enough to get information out of JIRA using JIRA when I watch our PO in planning meetings.