francis Atlassian Partner

Hi @Krithica Gowri Shankar Check following document which details an approach to know if the grid has been modified: https://wiki.idalko.com/x/hADOAQ

Exalate is an issue synchronisation tool allowing to synchronise defects from HP ALM to Jira (including 7.9.1) If you would like to have more information on the capabilities of Exalate - please feel free to book a meeting at https://exalate-demo.youcanbook.me Francis

(thanks for mentioning us @Alexey Matveev) Hello @Maheeza, There are different solutions on the marketplace - check following query https://marketplace.atlassian.com/search?query=issue%20sync We are the team behind Exalate (which is one of these solutions)…

Hi Paul, Aren't these requirements part of the general acceptance criteria of ongoing developments. In our case we do have test plans checking specific concerns such as security, performance, reliability. These test plans are currently documented on our confluence (and/or automated in our integration tests) Whenever for…

Hi Guido, Do you integrate through REST or SQL? In the latter case, you can use the multi level cascading field functionality offered in the table grid editor Check for an example here Francis

Hi Saritha, Bulk copying between multiple JIRA instances is at the core of Exalate - a Jira issue Synchronisation tool. If you would like to know or see more - just book a meeting on https://exalate-demo.youcanbook.me

Nic - thanks for mentioning Exalate This is a core use case of Exalate - a Jira Issue Sync solution. Take into account the other cases where the developers don't consider the issue as a bug, request feedback about some items, or have a similar issue. Establishing such workflow orchestration can become very interesting -…

Hallo Wasseem, We introduced compatibility with Sybase 15 and 16 in version 1.27.0 of the table grid editor (for server). The multi level cascading field is compatible with JSD. It allows to build a cascading field which extracts its data out or multiple databases ... Francis

You can also have a look at Exalate which is available on the marketplace. Escalating issues from one issue tracker to the next is part of its DNA and covers Jira Service Desk to Jira Software (and many other cases) With her flexibility, implementing advanced escalation paths is always possible. Francis

Like Nic says, there are a couple of solutions on the marketplace. Exalate (I'm part of the team building this product), allows to synchronise not only the stories but also epics, sprints, ranking - the whole lot. If you would like to see it in action, just book a meeting https://exalate-demo.youcanbook.me Francis

Hi, There are different solutions on the marketplace - check following query https://marketplace.atlassian.com/search?query=issue%20sync We are the team behind Exalate (which is one of these solutions) https://marketplace.atlassian.com/plugins/com.exalate.jiranode/server/overview It fully covers your use case, and we are…

Hi Mauro, Alexey mentions one of the different solutions to accomplish what you are looking for. There are different solutions on the marketplace - check following query https://marketplace.atlassian.com/search?query=issue%20sync We are the team behind Exalate (which is one of these solutions)…

> Our JIRA server is in cloud and SSO is turned on. Are you using Atlassian Cloud or are you using Jira Server on a hosted infrastructure?

There are 5 JIRA instances, 1 Service Desk and 4 Software Based on some criteria, tickets generated on the service desk need to be exalated to one of the 4 software instances. * Workflow needs to be orchestrated such that transitions on either end are reflected on the other end * I reckon that other fields such as…

Nic question is pertinent. Having one single system is way easier (in all dimensions) then multiple systems Still - whenever you're on a single system - you might want to orchestrate tickets and issues such that for instance comments added to a software project based issue is automatically added to the ticket and the way…

Hi Ananias, I'm with Exalate, one of the solutions Craig mentioned. Please feel free to book a demo at https://exalate-demo.youcanbook.me and we'll be happy to discuss your requirements and how Exalate can meet these. Francis

Here at Exalate - synchronization between diverse issue trackers is our daily food. The engine we are building allows for a flexible and autonomous synchronization in a reliable manner. We do have a program in place for organisations who would like to start synchronizing between diverse systems. Send us a mail (sales at…

Would you need the same functionality as the table grid editor, or just ensure that the data is included in the xml backup? Francis

Have a look at Exalate. Exalates comes with a script processor which allows you to perform any type of transformation, filtering or mapping. For instance to do this 'sync custom fields' - check out following page from our documentation:How to synchronize custom fields. You will see that almost any custom field mapping is…

You can also use Exalate which has the concept of triggers, which will pick up any issue that match a number of conditions and send the issue over to the other Jira Account and keep both issues in sync. Francis

You might also have a look at the atlassian docker builder which allows you to build docker images for any atlassian application. It is open source and available here We created a blog to show how it is being used https://www.idalko.com/atlassian-jira-upgrade-journey-using-docker-and-the-atlassian-docker-builder/ We are…

Check out scriptrunner. It provides a jql 'issuesInEpic' which allows you to select all the required 'line items' A jql (= advanced search) selecting your epics and underlying issues can be constructed such as issueFunction in issuesInEpics("project = ABC") or (project=abc and issuetype=epic) Hope this helps

Hi Danielle, You can always import a single project from backup. Check the atlassian documentation on the subject https://confluence.atlassian.com/adminjiraserver073/restoring-a-project-from-backup-861253833.html Francis

You can also use Exalate to do a live migration between both instances. Check following documentation page for more details https://docs.exalate.com/display/ED/Project+migration+using+Exalate+add-on

Hoi SysteemBeheer, Or you can contact us (Exalate). Exalate is an issue synchronisation solution allowing to synchronise issues between different issue trackers. We are currently supporting Jira and HP QC, topdesk is currently in our long term roadmap - but that can change. Contact us by sending a mail to…

Have a look at Exalate. It is an issue synchronisation tool supporting the synchronisation between agile projects. The following movie shows how this would work between jira server projects, but the same applies between server/cloud, cloud/server and cloud/cloud https://www.youtube.com/watch?v=U7dzYzwyL30&feature=youtu.be…

Could you check what the renderer of the comment field is. * Admin -> Field Configurations -> The field configuration of your project -> Find Comments It should be wiki renderer The wiki renderer will identify issuekey's and convert it to a link

Absolutely - send a mail to support@exalate.com, and we'll pick it up from there.

One of these is Exalate (available for cloud and server) To show off - here is how Exalate can be used to synchronise agile projects including epics, sprints, stories - the whole lot https://www.youtube.com/watch?v=U7dzYzwyL30&feature=youtu.be

Hi all, The issue appeared to be a conflict between the table grid editor and Intenso's Dynamic Forms. Intenso took care of it, and upgrading the dynamic forms should resolve the problem If you still encounter problems - let us know by raising an issue on our JIRA Francis