nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

automated sync is required between ENGJIRA to Client JIRA

vandana.sharma

some automated sync is required between ENGJIRA to Client JIRA for items where if it is marked as CLOSED in Internal JIRA with a fixVersion, then Client JIRA shall be automatically updated to “Pending Upgrade” or if it is without a fixVersion then it shall be auto-updated to “Pending BQA Testing” in client JIRA to ensure these can be excluded using a filter.

Accepted answers

Syed Majid Hassan -Exalate-

Hi @vandana_sharma

This is Majid @ Exalate.

Your use case is pretty interesting and should be achievable if you set up a synchronization between the two Jira systems. You can use any integration app like Exalate to set up this use case up. You can automate ticket creation on client jira, and then use your fixVersion and status to trigger the relevant change on their side.

Please let me know if you want to discuss the use case in depth and I would be happy to engage further.

Thanks

Majid

All comments

Jack Brickey

Hi @vandana_sharma , welcome to the community.

If you are referring to syncing issues between two different instances then you should consider an add-on to achieve this. One such addon backbone-issue-sync-for-jira looks promising though I have never implemented personally.

While you could attempt to achieve something through automation it would be extremely difficult and prone to breaking. If you wish to attempt something like this then you would need to create automation on both instances one that would create (via email) the issue and add comments (via email) to the other instance. The receiving or client instance would need to trigger on comments and look for specific text and update the ticket accordingly.

Matthias Gaiser _K15t_

Adding to @Jack Brickey's answer, if you actually go the automation way, you could use the send web request action and webhook trigger for communication between the instances.

However, it really is cumbersome to setup complex synchronization scenarios. If transitioning the issues is all you want to do, this might be a possible way to go.

I'm part of the team behind Backbone Issue Sync - and such an issue sync app is another automated way (with less maintenance for you) to solve your use case. I suggest you try it out yourself to see what better meets your needs.

Katarzyna Szumilas_Deviniti_

Hi @vandana_sharma

If you are indeed interested in 3rd party synchronization tools I can recommend the one recently developed by my team - Issue Sync Lite.
The app synchronizes issues between two cloud instances (or projects) and automatically creates, copies, and updates their data like fields, comments, attachments, or workflow transitions.

You can also set JQL conditions to decide when the synchronization should happen (for example when a given issue reaches status CLOSED and fixVersion is not empty the synchronized issue will be transitioned to “Pending Upgrade").

If that sounds interesting, feel free to try the app or book a demo via Calendly.
Best regards,
Kasia from Deviniti

Syed Majid Hassan -Exalate-

Hi @vandana_sharma

This is Majid @ Exalate.

Please let me know if you want to discuss the use case in depth and I would be happy to engage further.

Thanks

Majid

vandana.sharma

Hi, lets discuss this further

Syed Majid Hassan -Exalate-

If you have some specific questions, I would be happy to answer them. Otherwise, the best approach would be to explore our website and book a demo to discuss your use case further.

Thanks

Majid

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud