Hey everyone, I'm in a bit of a pickle and could use some advice. Our company has two Jira Cloud setups - one for the dev team and another for ops. We've got the same project running on both.
The thing is, sometimes the dev team creates tasks that the ops folks need to be aware of and work on. I'm wondering if there's a way to automatically copy or sync these specific issues from the dev Jira to the ops Jira.
Has anyone tackled this before? Are there any built-in features or add-ons that might help? I'm not looking to merge the two instances, just need a method to keep certain tasks in sync.
Any tips or tricks would be greatly appreciated! Thanks in advance!
I’ve been in a similar situation before, and I can tell you it’s not an easy problem to solve. We ended up using Jira’s REST API to create a custom integration between our two instances. It took some development effort, but it worked well for our needs.
We set up a script that would run periodically to check for new or updated issues in the dev Jira that met certain criteria (like having a specific label). When it found matching issues, it would create or update corresponding issues in the ops Jira.
One thing to watch out for is maintaining the relationship between the original and synced issues. We added custom fields to store the ID of the corresponding issue in the other instance.
If you’re not keen on custom development, you might want to look into third-party tools like Exalate or Backbone. They specialize in Jira synchronization across instances.
Just be prepared for some challenges around permissions and field mapping. It’s not always straightforward, but it’s definitely doable with some effort.
I’ve dealt with this exact issue in my previous role. We found that the Jira Misc Workflow Extensions (JMWE) app was incredibly helpful for this scenario. It allows you to set up automated workflows that can create or update issues in another Jira instance based on specific triggers.
We configured it to automatically create a mirrored issue in the ops Jira whenever a dev issue was labeled with ‘ops-required’. It maintained a link between the two issues, so updates on one side would reflect on the other.
The setup process was relatively straightforward, and it didn’t require any custom coding. However, you’ll need to ensure both Jira instances have JMWE installed and configured properly. Also, keep in mind that this solution does come with a cost, as JMWE is a paid app.
If budget is a concern, exploring Atlassian’s native ‘Automation for Jira’ feature might be worth your time. It’s not as powerful as JMWE for cross-instance syncing, but it could potentially meet your needs with some creative rule-setting.
hey markseeker91, have u looked into zapier? it can connect different cloud services, including jira. i’ve used it to sync stuff between trello and jira before. might work for ur situation too. just set up a zap to watch for new issues in dev jira and create matching ones in ops jira. pretty easy to setup, no coding needed.