Andriy Dekhtyar _Rozdoum_ Atlassian Partner

 Hi @Mohammed Patel as colleagues mentioned there might be different aproaches - synchronisation, where Backbone, Exalate, issuesync and others might be of help - composing a confluence page and bringing data from different instances - if you just need kind of overall report - or solutions like Watchtower that will allow…

Hi William You have number of addons on marketplace that make "jira sync" ( this would be a good key to search) Alternatively to sync you can use our addon - Watchtower for Jira to see and interact with issues on remote Jira without leaving your comfortable environment Take care Andrey

Hi @Christy Miller check this out , Time report from remote Jira - may allow you to combine timesheets from 2 different Jira instances in one report. If you need some help, please book a demo, so I can guide you through the setup Regards Andrey

Hi @Sandeep Sekhar As Matthias correctly mentioned one option would be achieve what you want with issue sync apps to exchange data, as alternative I may suggest to make a bridge between two instances and then see and make all interactions with issues on remote Jira with help of Watchtower app. P.S. Well, I am from…

Hi @Tom D_Eletto Depends on what you need to do. On top of what Benjamin suggested - I may advice taking a look at our addon - Watchtower - Bridge for multiple Jiras. It may allow to achieve visibility of remote instance within fraction of time Regards Andrey 

Hi Adam As alternative to cloning you can use Watchtower addon that would allow you to bring data from both Jiras in one agile boards and work seamlessly. If you feel necessary we can organize a demo for you Regards Andrey Watchtower team

Hi @Andrei Tuch Well, another option might be to consider WatchTower , even though you won't get unified JSD queue - you can get consolidated view across multiple Jira/JSD instances from one place without interference on customer's Jira side. Be ready to address questions from the team behind WatchTower in case you have…

Hi @christacap Based on the context - what do you mean with external party's Jira board. If you tempt to refer to external Jira then your choice would be either - synchronization of projects, as Stephen mentioned or - solution Watchtower for Jira that can consolidate data from multiple Jira's into one Agile board. Regards…

Hi Lisa the easiest way would be to create a JQL filter combining issues from all the projects you need. Once that is done you can point AgileBoard to that saved filter and get the result Regards Andrey

ehm.. then probably it's not "priority", but "ranking" still, at the moment not possible, but thanks for idea - we will put that into backlog. Thanks for idea as possible workaround - you can organize that with help of swim-lanes, where you define what to put into "blocker" smiwlane with help of cross-Jira instance JQL in…

Hi @myadav On behalf of a team behind WatchTower let me point you that with a card on WatchTower board you are one click away from opening ticket in a new tab, where you can change not only priority, but any other field of the issue. For doing that just click on a link behind issue-key Not implementing that in WT was an…

Well, to my knowledge - customer willing to use your Jira - is quite a common case. Federation or multiple Jira instances for "data protection" might be just too-much. Did you consider just permissions, user-groups and proper roles setup? Regards Andrey

Hi We have implemented similar solution with one to many links stored in the custom field value in the specific format. The value stored thereafter was parsed to retrieve info relevant to relations. Hope this helps Andrey

Hi Anand Not directly as JQL is bound to to one Jira instance. At the same time with Watchtower addon ( yes, I am from Watchtower team) you can create an agile board combining issues from several Jiras. Once you have that you can run cross-Jira JQL search to filter issues on the board you are interested in. At the moment…

Hi @Raj R Managing a project where tasks are spread across multiple instances might add complexity to project management. At the same time there are number of addons that might help you to address that issue if you want to achieve transparency and visibility of the process. One way to address that from point of…

well you can achieve that with help of addons. Though not gadget specifically, but.. You can try to sync Jira ( there are few addons for that) or you can use our WatchTower addon that allows you to have a agile board showing issues from remote Jira instance. Should you have further questions - I be ready to address them on…

Well, talking about consolidation - I would advice taking a look at our solution - WatchTower for Jira - it can bring issues from different Jira sources into one agile board, where you can work the usual way. As alternative - you can try to setup synchronization between instances, or migrate them into one instance

hi @Cihan Ünsal As alternative to above mentioned options - you can also consider our solution - WatchTower for Jira - that allows you to have agile board pulling issues from remote Jira sources including JSD. This way you can have an overview and some form create cross links between issues in different Jiras. Andrey 

Hi Darlene I am not sure what information you want to see on dashboard, but I would recommend checking functionality of our addon - WatchTower for Jira. It allows gathering data from multiple Jira sources into one Agile board. Functionality of dashboards is still in pipeline, so here it would depends on what exactly you be…

Thanks, Rachel, great advice! 

Hi @Matthias Gaiser _K15t_ Thanks for feedback, to address your questions: >Does every user who views the Watchtower board need an account in every Jira? Well, it depends. WatchTower board can be shared by board admin with other users. There are two modes of sharing : view only and edit mode. In "ViewOnly" remote source is…

Hi @Roberto Ialino Looks like what you are trying to achieve is directly addressed by our addon - Watchtower for Jira. It explicitly address consolidating data from different Jiras into one agile board. Alternative approach might be setting up Jira to Jira sync, but that would be another order of complexity Hope this…

Hi ariel@Seraphim-opt.com alternatively to sync you can consolidate and pull specific data from one instance to another. Our addon - WatchTower for Jira allows you to create an agile board with issues from different remote sources and work as it is your local board. Confluence is a different story, indeed Regards Andrey

Hi @Iztok Or you can take a look at WatchTower that allows you to consolidate issues from multiple Jiras into one agile board without actually synchronizing instances Andrey

Hi @Heshan Manamperi Alternatively to jira sync you may also try to access issues from one jira inside the other. As a sample of what add-on Watchtower for Jira can provide you - you might have agile board on one instance with issues from both Jiras with cross-links between issues from different Jiras Cheers Andrey

Hi @Gregory Carman Alternatively to Jira to Jira sync you might take a look at our solution - WatchtTower that allows consolidating data from different Jira source into one agile board. This allows seeing, updating, transition through workflow etc. More over you can share WatchTower board within your team with different…

Hi @Frank Well, WatchTower is not a migration tool. Migration is the thing you need to do as independent procedure. The questions which WatchTower raises is - whether you actually need this migration? Some of your users may use cloud instance, while other can access cloud from their server instance instantly. This can run…

Hi Frank What particular are willing to achieve with integration? If your main concern to enable users from one Jira instance be able to access data from the other one - I may recommend taking a look at WatchTower for Jira that aims consolidating data from different sources into one board Regards Andrey

Hi @Maik Himstedt In the meanwhile may I offer you to take a look at our addon - WatchTower for Jira - it may allow you to consolidate data from different Jiras into one board. For some of our customers this turns out to be alternative for migration and allows to work nicely with remote Jira instances Regards Andrey

Hi @Saravanan VC If you are dealing with projects spread over different Jira instance - you actually have a number of choices 1. The approach you suggested - migrate projects into a single instance. In this case you get the most consistent setup, but migration might be a challenge. You will need to deal with dependencies…