Shared data on several instances or tenants

[Diemunsch Jean-Baptiste]

Hello,

I am not a very experienced Jira software and have specific needs for the organization I am now working for.

SItuation is :

- A project development team is already working with Jira software and confluence for the develpment of a software platform. Scrum projet is set up nicely and work ongoing.

- This dev team is a partner of the company I am working for. Meaning their Jira instance is their own. The dev cycle starts when stories are validated.

- My organization needs Jira software for managing its own project as well as communicating with Jira outside for the externalized developments.

- But dev company does not allow to use their tenants for externals outside dev activities. So I have to work on antother tenant

So I need :

- Jira software to manage work prior to externalized dev (define Epics, product ownership).

- Share Epics, stories cross tenants.

I hope that makes sense.

Thanks.

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Community!

You could connect the two systems with an Application link, which would make them aware of each other and provide easy linking between issues on the two systems, but all you will be able to do is link issues (refer to issues in the other system)

Because the two systems are separate, you won't be able to use issues in one system as though they were in the other one.  Epics in system A can't contain stories from system B  An Epic or story in A will not appear in B, in boards, reports, or anything other than as a link on an issue that does exist in B.

What you might want to consider is a copy of the project(s) you want to work on.  There are a number of synchronisation apps in the marketplace that can allow you to link two projects on separate systems together and have them synchronise (the projects do not even need to be identical, the sync can be set up to do issue-to-issue and map fields if they have different options and so-on)

[Diemunsch Jean-Baptiste]

Hello. I thank you a lot for your detailed answer.

By any chance would you have any recommendations for these synchronization tools?

Thanks again

[Nic Brough -Adaptavist-]

Personally (not an Adaptavist recommendation, as I try not to advertise), I have a soft spot for K15t's Backbone. 

I may be biased by having spent time with K15t at summits and ACE's and having had a few chats with them where I've said "I have a client with this problem" and they've added something to it that fixes the problem for me.

But I've had a lot of success with Exalate as well.

There are some other apps that might suit you better too, but I've not really tried them in anger, so I can't judge them at all.

My recommendation is to look at all of them, but start in the marketplace and look at the ones that have large numbers of users and good ratings.

[Syed Majid Hassan -Exalate- · Accepted solution]

Hi @Diemunsch Jean-Baptiste

I believe that you are duplicating a lot of work while maintaining the issues on 2 different instances/ tenants! With a bi-directional synchronization setup between the two Jira instances (project and dev), the workflow would be as follows:

- Issue is created in project Jira and all the validations etc. are performed. 

- Issue is then sent over to the dev Jira via some automation (status perhaps). 

- Dev team work on the issue in their Jira instance and updates are synced back to project Jira (if you want them to).

This way you will maintain the autonomy while saving yourself from the manual duplication efforts. I work as a Pre-Sales Engineer with Exalate and would happily recommend our tool to add value to your business processes by introducing this automated integration to your workflow. 

Happy syncing!

Thanks

Syed