Services
Are you spending dozens of hours for seamless data transfer from Jira manually or through export/import operations?
Integrating platforms service
We provide integration of Atlassian products with third-party systems of a different kinds, like modeling, issue tracking, invoicing, and reporting tools, as well as knowledge bases and CRM systems. Our aim is to make your business processes smooth, seamless & transparent across all tools.
How it all began?
We were using Atlassian Jira & Confluence since 2004, adding various invoicing tools and CRM systems to the list of products that helped us to grow. First automation was also an internal one aimed to save time transferring data from Jira into accounting system Freshbooks and vise versa. The next integration was for the sales department. One of the CRM tools we’ve used, Streak, was integrated into Jira with a so-called connector.
We at Rozdoum believe that the future belongs to those who successfully integrate the work of many tools and services, gathering data into one agile process, which is easier to scale and correct.
Why integration?
If your company has more than one department (probably 90% have more than one), you’re definitely used or will be using several tools in each of them. Sales teams use CRM systems, email marketing tools, apps for presentations, calls recordings – you name it. Development teams usually use task trackers, like Jira. If you’re a service company, sales people might be sending tasks for estimation to the development team. If they are doing it manually now, they need to keep both their CRM and task tracker up to date with all the data. As for successful Enterprise Asset Management, integration is essential, since it is very difficult to achieve systemic and coordinated management when dealing with many tools.
Just imagine they won’t need to do that and those tasks updates that are in Jira appear in sales CRM. Sounds good? That’s why integration of those tools is important: saving time of your employees doing copy-paste tasks and keeping both systems up to date.
Improving team productivity is one of the primary reasons for integration. Our Fiix case is a good example of such integration. This platform is a Cloud-based CMMS Software, which was used only for internal use. The lack of an external interface prevented users from creating work orders, searching assets, choosing issue types etc.. Our client wanted to combine this platform with Jira Service Desk.
It was important to create a working external interface in which users could fill in all the possibly required fields. After that, this data was synchronized between the two systems. For the latter task, a separate Jira Cloud application was developed, which was engaged in data synchronization between the two systems. The integrated result was a custom-developed Jira Add-on, which made it possible to significantly increase the productivity of Fiix, as clients received a convenient external portal to use.
Perhaps the main problem we faced was the direct assets search via API in Fiix. It was decided to use the Lucene index, which allowed users to search for assets much faster and safer.
Professionals are aware of how much information travels constantly from tool to tool on large projects. Such data must be constantly monitored. By integrating- different tools and platforms we achieve seamless flow for business processes. Atlassian ecosystem, the entire data flow will become transparent, scalable, and traceable.
We believe that there are no one-stop solutions for all issues. Therefore, at Rozdoum we specialize in developing custom integration solutions for each individual case, Our capacities and experience allow us to integrate any service, at the request of the client. Below, we invite you to familiarize yourself with some of our integration cases.
Integration cases
Several examples of successful integration should give you additional insight into our service.
Confluence to Salesforce Integration
Custom add-on development to integrate Confluence with Salesforce.
Salesforce is one of the most popular tools among Project Managers. The Confluence Database, in turn, is used by Atlassian experts as a wiki base for projects. We at Rozdoum managed to create a custom add-on that successfully migrates and syncs Confluence content to Salesforce. We can implement this solution for any client who works with both tools. The purpose of this integration is to achieve smooth Confluence data live synchronization and update with Salesforce content.
By placing back-end hosting on AWS Lambda, we managed to achieve live synchronization of a huge amount of data, so a heavy load is not a problem.
Another custom solution for data migration from HP ALM to Jira. The main purpose of the tool is to automate the process of transferring defects and test management data from HP ALM to Jira. In order to create such a tool, our specialists had to carefully study the entities of the HP ALM and Jira, in search of any similarities. The result was a decision that divided the entire process into two main stages.
At the first stage, a wizard, specially designed for the transfer of projects and defects, analyzed the existing projects in the HP ALM and created the corresponding projects in Jira. The project in Jira was created with the same fields that it had in the HP ALM. After creating a project, the tool automatically migrated defects from HP ALM projects to newly created Jira issues.
Due to the fact that Jira does not have its own test management toolkit, we in Rozdoum decided to migrate test management data using third-party add-on with a massive API.
The app allows standard actions managing Jira issues directly from the Confluence page.
The app gives you the ability to view detailed issue information as well as listing, edit, transition and create Jira issues within the Confluence page.
The add-on saves time and ensures users work with the context on Confluence without switching.
This case is an example of the successful integration of Microsoft Project and Jira. Specifically: data migration between two systems thanks to a third-party custom-developed parser. The task was to migrate the MPP data from the MS project to Jira, including such parameters as durations, dependencies and assignees of all tasks.
The result of the work was a custom application written in Java 8. It parsed the MPP file placed in Jira and created tasks with similar data, including those that we listed above. We managed to ensure deep interaction of the application with the Jira structure.
Diagram of the integration processes:
Collect client's requirements
Come up with a way to integrate, choose approach(migration, interaction, reporting. etc)
Investigation of the tool's functionality
Investigation of REST API of each tool
Mapping Atlassian entities to entities of the tool
Implementation
Integration is the future
We at Rozdoum believe that the future belongs to those who successfully integrate the work of many tools and services, gathering data into one agile process, which is easier to scale and correct. A significant reduction in time due to seamless data flow between different systems and omitting loss of data during the synchronization process allows you to achieve greater productivity in your business processes. And the automated integration of various services allows you to reduce the amount of manual processes, and frees your specialists for more serious or creative work.
Which services do you use alongside with Atlassian ones? Which are you updating manually?
Just name them and we’ll dedicate 1 hour to see how they might be integrated.