Hey everyone,
I’m trying to find a way to keep Redmine and JIRA in sync. Does anyone know if there’s a tool or plugin that can do this?
Here’s what I’m hoping to achieve:
- When I make a new ticket in Redmine, it automatically shows up in JIRA too.
- If I create a ticket in JIRA, it appears in Redmine as well.
- Updating the status of a ticket in one system updates it in the other.
Has anyone set up something like this before? Any tips or recommendations would be super helpful. I’m not sure where to start, so any advice is appreciated!
Thanks in advance for your help!
I’ve actually tackled this issue before in my previous role. We ended up using Exalate, which is a robust synchronization tool that works well with both Redmine and JIRA. It allowed us to set up bidirectional syncing for tickets, including custom fields and attachments.
The initial setup took some time, as we had to map the fields between the two systems carefully. However, once configured, it ran smoothly with minimal maintenance. One thing to watch out for is potential conflicts if the same ticket is updated in both systems simultaneously.
We also had to be mindful of user permissions and ensure that the sync didn’t inadvertently expose sensitive information across systems. Overall, it significantly improved our cross-team collaboration and saved us countless hours of manual data entry.
yo, i’ve used go2group’s sync for jira plugin before. it’s pretty solid for keeping redmine and jira in sync. handles new tickets, updates, and statuses both ways. setup can be a bit tricky tho, so be ready to tinker. also, watch out for weird sync issues if ur teams use different workflows.
Having worked on a similar integration project, I can attest to the complexity of synchronizing Redmine and JIRA. One solution we found effective was using Zapier, a web-based automation tool. It allows you to create ‘zaps’ that trigger actions in one system based on events in another.
For instance, you can set up a zap that creates a JIRA issue whenever a new Redmine ticket is made, and vice versa. The tool also supports updating ticket statuses across platforms. While it requires some initial configuration and possibly a paid plan for more complex setups, it’s generally user-friendly and doesn’t require extensive coding knowledge.
However, be prepared for some limitations. Real-time synchronization isn’t always perfect, and you may need to handle edge cases manually. Also, ensure you have a clear mapping strategy for fields that don’t directly correspond between the two systems.