Tracking requirements across multiple instances of JIRA

[PaulH]

We are setting up a programme of work, and I will be inputting the high-level requirements into a programme instance of JIRA. However, these requirements will be broken down into lower-level requirements that will managed by various teams across different instances of JIRA (not just different projects in the same instance of JIRA). What options are there for tracking the requirements and ensuring that we can see the true status of the delivery of the high-level requirements? Thanks

[Jehan Bhathena · Accepted solution]

Hi @PaulH ,

You can initiate an App link between the jira instances https://support.atlassian.com/jira-cloud-administration/docs/use-applinks-to-link-to-atlassian-products/, once done, when ever a ticket from the other instance will be linked (using the Weblink option) the status and overview of the ticket will be visible to anyone who has access to both the sites.

Hope this helps.

[Matthias Gaiser _K15t_]

I'm backing up @Jehan Bhathena's answer.

If it's enough for you, I'd also create application links between all the instances. Then you're able to remotely link the corresponding issues together and will see their updates in the respective issues.

However, the issues from the other instances won't show up in JQL search results or other statistics within your programme Jira.

If you're looking into a deeper integration, I'd suggest using an issue synchronization app. These apps offer you to replicate your instance from the lower-level Jira instances to the programme-level Jira or also the other way round and keep all interesting fields for you in synchronization.
With this kind of integration, you can use all usual Jira reporting ways to know about the actual state of your issues.

I'm part of the team behind Backbone Issue Sync, we're concentrating on making issue synchronization as easy as possible. Let me or our support team know if you have any questions about it.

Cheers,
Matthias.

[PaulH]

Great - thanks very much, both. Useful options to explore here.

[Dhiren Notani_Exalate_]

Hi @PaulH ,

Thanks for sharing your question here, I am Dhiren from the Exalate Team.

I would recommend you to use a completely customizable bi-directional integration solution like Exalate in this case.

It's possible to sync your issues (Epics,Stories,Tasks etc) from one project to a different project(on a different instance) and keep the issues in sync for tracking them.

With the Groovy based scripting interface you can choose what information will flow through the tickets and it's very flexible as well.

Do let me know in case you have any more questions.

Thanks, Dhiren