francis Atlassian Partner

Hello Sandrine, There are a couple of free apps on the marketplace which allow to automate such settings, but they not always cover all requirements. Is this in the cloud or in server - I can then provide some links. Alternatively you can build your own app using the atlassian SDK - more information here…

(I'm with the team of Exalate) We have once setup a configuration which we call a star network The star network is an exalate configuration where one central master JIRA is used to raise program level issues which then fan out towards the different slave JIRA's which are used to handle product/component level issues. The…

Good morning @Rangarajan Parthasarathy Exalate is an alternative issue synchronisation solution. I'm also biased as I'm working for the team that builds the add-on A number of our customers have been implementing JSD to JSD synchronisation, and it gets really interesting when considering how internal comments need to be…

You are on Server - right? Did you move the custom field to the top of the screen

We are using a 'Message Edit' custom field and set the default value to <style> .comment-input { display:none; } </style> and add this to the screens where we want to remove the comment input box.

Hello all, I'm part of the Exalate team, which is an issue synchronisation solution allowing to sync boards and all entities on that board, including epics, stories in the epics, sprints, versions, ranking ... Here is a video showing how exalate can be used for this use c https://youtu.be/U7dzYzwyL30 Check out more details…

Exalate requires to have it installed on both sides. The reason is that you want to remain autonomous between the two systems. Whenever your customer is doing a configuration change, you don't want to be affected or the way around. There are solutions to do the synchronisation from one side, but that is an approach which…

Hi @Ammar, Stories, tasks and sub-tasks are Jira entities. (We're the developer of the Exalate Jira Issue Sync app) What you're describing is a pretty common use case for our app. You'll be able to synchronise any issue data of one of your instances over to the other instance. This will happen in real-time. That way,…

Hi Jouni, I'm with the team behind exalate. FYI - you can use automation for Jira to trigger synchronisations Let us know how we can help - always welcome to setup a conference call to discuss ins and outs of your use case. Please feel free to book it at https://www.idalko.com/exalate-book-demo Francis

Hi @Shamshuddin Althamash K, The Table grid editor for server app has a multi level cascade where the drop down lists can made dependent on issue values. It is service desk compatible Check out some examples here Francis (PS. I'm with the team that builds this app)

Hi Stephen, Thanks a lot

Also have a look at the Exalate Network pricing model You want to avoid that each of your customers have to buy a license of the app and the Exalate network license model allows you to purchase just one license. Your customers will still need to install the app on their side as this is essential for security and autonomy…

Hi, We're the developer of the Exalate Jira Issue Sync app. What you're describing is a pretty common use case for our app. You'll be able to synchronize any issue data of one of your instances over to the other instance. This will happen in real-time. That way, you'll always be in the loop on progress status, comments,…

We're the developer of the Exalate Jira Issue Sync app. What you're describing is a pretty common use case for our app. You'll be able to synchronize any issue data of one of your instances over to the other instance. This will happen in real-time. That way, you'll always be in the loop on progress status, comments,…

Hi @Esther Strom_ ACP-JA (I'm with the team working on Exalate) You can use Exalate in case you would decide to separate out the JIra Service Desk and the Jira Software. Exalate would then sync the Jira SD tickets on one instance with the Jira Software issues on the other instance. It is a good question if 2 factor…

Ah - yes. It is for development and testing purposes. 

You should have a look at the image provided by codeclou https://github.com/codeclou/docker-atlassian-jira-data-center It works wonderfully well - and fully documented.

(@Thomas Varghese I obviously missed your comment) Release Management is a pretty wide field, and the workflow can depend on the type of product you release. Is it hardware, software - a combination. What are the expectations?

(this is a pretty old question - but I guess still valid for a lot of people The crux of this question is in > We also want to migrate all project schemes and configuration. Issue synchronisation tools are not meant for this type of migrations. (I'm with the team that builds Exalate - also a synchronisation solution) You…

(I'm with the team that builds Exalate - also a synchronisation solution) You might use an argumentation build around the fact that having a human copying data is not a guarantee that sensitive data is not leaking. Human do make mistakes. Using a systematic approach for exchanging information brings more control on what…

OK - thanks for letting know

Hi We're the developers of the Exalate Jira Issue Sync app. What you're describing is a pretty common use case for our app. You'll be able to synchronize any issue data of one of your instances over to the other instance. This will happen in real-time. That way, you'll always be in the loop on progress status, comments,…

Can you detail out the error and send it to support.tge@idalko.com. We'll take it from there. Francis

And what is following query returning issue in grid("Table Grid Editor_Test", "ifixversion= '123'")

Excellent if you require some help or if you encounter bumps, you can engage in different ways * By sending a mail to support@exalate.com * By booking a demo or support meeting through https://www.idalko.com/exalate-book-demo Francis

Hi @Iztok How would the issues be created. Are these created in every jira independently, or are they created in one jira and then escalated to the next? Francis

Hi @Narasimha A Although that I'm with the team of Exalate - another synchronisation solution (next to bb) - there is a small caveat when using such solution for migration. Synchronisation and migration are not the same use case. In case of migration, you want to carry over all the data such that you have an identical…

Thanks @Mohamed Benziane @Jon You can find more information on the table grid editor * For cloud * For server A sample grid More information available at our documentation site - here

Hi @Alexey Matveev When implementing a migration and thinking about Exalate - you have to be carefull. Exalate is a synchronisation tool optimized to sync as fast as possible any change that is applied on an issue. It is less a migration tool for some of the migration requirements: * configuration migration You want to be…

(Thanks @Mohamed Benziane) Hi @FE Williams , If you would need any more help - don't hesitate to send a mail to support.tge@idalko.com. Francis