We have two JIRA projects. One for members outside of development and one that is internal.
In the external project users will request new features, report bugs etc.
The internal project includes these types and also other types used internally by the development team.
I am trying to set up a process where an external (i.e. Marketing) can request a feature and a specific release that they desire. Upon ticket creation a corresponding ticket is created in the 'internal' project with appropriate fields passed to the internal project. This all works fine with a plugin.
I would like to have these two tickets linked in such a way that common fields / status in both projects stay in sync. For example, I want the the cloned ticket in the internal project is 'Closed' I want the originatating ticket to also close.
Is it possible to implement such a sync. mechanism?
yes, this is possible. You can accomplish this task with Backbone Issue Sync for JIRA. It allows you to configure which issue types, fields and workflows you want to map.
There are also some other addons available which should do the job. Have a look here: https://marketplace.atlassian.com/search?query=issue+sync
As Matthias is saying, there are multiple solutions for synchronisations, each with there own advantages and disadvantages.
We are building Exalate - issue sync for JIRA and Cloud - which allows to implement the most complex synchronisation cases (through scripting)
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs