Hey everyone,
I’m trying to set up a connection between two JIRA instances using email. One is running version 4.2.1 and the other is on 4.3.3. Both have their own custom fields.
What I want to do is:
- When someone makes a new issue in JIRA A, it sends an email to JIRA B to create the same issue there.
- If someone updates an issue in JIRA A, it emails JIRA B to update that issue too.
Basically, I need them to stay in sync all the time. Has anyone done this before? Any tips on how to set it up?
I’m not sure if the version difference matters. Also, I’m wondering if there’s a way to make sure the custom fields transfer correctly between the two systems.
Thanks for any help!
I’ve actually implemented a similar setup in my previous role. While email notifications can work, they’re not always reliable for real-time syncing between JIRA instances.
Instead, I’d recommend looking into JIRA’s REST API. It’s more robust and allows for better control over data transfer, including custom fields. You can set up a middleware service that listens for changes in JIRA A and pushes them to JIRA B via API calls.
The version difference shouldn’t be a major issue, but you might need to map fields carefully, especially custom ones. Also, consider potential conflicts if both instances allow editing. You may need to implement a conflict resolution strategy.
One caveat: this approach requires some coding skills. If that’s not feasible, there are third-party JIRA sync tools available that might suit your needs better than email notifications.
hey, i’ve done smth similar before. email can work but it’s not ideal for real-time sync. have u considered using jira’s api instead? it’s more reliable and handles custom fields better. u might need to write some code tho. also, watch out for conflicts if both instances allow editing. good luck!
While email notifications can work, they’re not the most efficient solution for syncing JIRA instances. I’d suggest exploring JIRA’s REST API for a more robust integration. It offers better control and reliability, especially for custom fields.
The version difference shouldn’t be a major obstacle, but you’ll need to carefully map fields between the two systems. Consider setting up a middleware service to handle the synchronization process. This approach requires some programming skills, but it’s more flexible and reliable than email-based solutions.
Be aware of potential conflicts if both instances allow editing. Implement a clear conflict resolution strategy to maintain data integrity. If coding isn’t an option, look into third-party JIRA sync tools that might better suit your needs.