Comment on page

Technical FAQ

Can I sync projects within one instance (e.g. within one Jira)?

Yes, this is supported. The setup of that integration is identical to the setup of projects synchronization between different Jira instances.

Can I sync Jira Cloud with Jira Server?

Yes. Integration of all Jira version combinations is supported. E.g. you can integrate Jira Cloud with Jira Cloud, Jira Cloud with Jira Server, Jira Server with Jira Data Center etc.

What Jira versions are supported?

We support Jira Cloud and Jira Server / Data Center (DC) >= 7.0

Is polling or pushing changes (issues) that should be synchronized? is working in polling changes mode. At a given interval, is fetching changes from the integrated apps. Read more in a Period changes fetching section.

What additional support do you offer?

The Standard SLA is 24h response time. For customers with premium support, except for standard support channels, we also offer invitations to our Slack and faster response time. All that to provide you with direct access to the Tech team of our product, which can help or resolve your issues when they appear.

Do you provide built-int Self Monitoring and High Availability features for On-Premise deployment?

Not at this moment. You can use one of the tools from the following list You can configure the tool to alert you when the server or the installed platform encounters any errors.

Is a standalone platform?

Yes. It is a standalone platform separated from the Apps it integrates (including Jira). Jira apps are only used for Licensing purposes, but the whole configuration, UI, and synchronization logic is stored and performed outside of Jira. That's why for Jira Server / DC which are behind a firewall it's essential to use the On-Premise version of Read more on the Architecture pages.

Is the On-Premise version Dockerized?

Yes. The On-Premise version is built up with few different tools like PostgreSQL, NGINX etc. To run it, you need docker-compose. Contact us at [email protected] to learn more.
To speed up the time of the installation and to provide you with the best possible experience it is suggested to use the Dockerized version of the during the trial period.
For production purposes, we still recommend using Linux VM-based installation.

If the customer is not able to have a hole in a firewall, do they need to host in their own servers?

Yes, you need to open a port in a firewall - or you need to host it yourself.

How to sync the huge amount of data fast?

You can set up integrations in parallel, creating multiple integrations threads, and then you can run those threads at the same time. Each integration/integrations will be run on separate threads so they will not wait with the start before the other finish.

Can you write additional scripts (transmission/receiving) like you can in the Exalate?

We do not provide scripting like Exalate. With time, scripting becomes very complex and can provide unstable behavior. In the end, it's usually hard to maintain. We are supporting variables and logical conditions. Using the variables you can build a new value for the field, in a dynamic way. For example:
e.g. ${item.title} will be translated to the value of the title field. That way you can e.g. combine few values into a one
Our UI should cover most of the needed use cases. If not contact us at [email protected] and we will do our best to cover the use case you have.

Can you sync project settings?

Not now. We are focusing on issues with data synchronization. Although we are receiving more and more questions regarding this so follow the Roadmap.

Can you sync apps from one Jira to another one?

No. We are not planning to implement that feature.

What about custom fields of apps that I have installed in my Jira?

Custom fields can be synchronized as all other standard fields of Jira. If you will not see the custom field on the fields list to map in the platform, contact us at [email protected]

What if we would need custom development, to add some extra features for us?

Contact us at [email protected] and describe your use case. If we will find it beneficial for the whole product, we will most probably add it to the roadmap.

Not all tickets are needed to be migrated, we need to filter out only some of them. How do you approach this?

When you are setting up the integration, for each of the apps you can provide additional query which will be appended to the request sent to the app when searching for items to sync. When this query is provided, the migration feature will use it. This way, you can filter out items that should be picked up for migration.

What do we need to set up in the tools to be able to use getint?

Jira Cloud - install one of our Jira cloud apps. Then you can access from the Apps menu.
To build up the integration, in both cases you will need to have the credentials of the users of the apps you want to integrate. E.g. if you integrate Jira Cloud and Asana, you need to have email address + the token of the user existing in Jira, and the token of the user in Asana. Then we can use those credentials to fetch all configurations needed to build up integrations and later on perform syncs.
For Jira Server - you need to install on the Linux machine if your Jira Server is behind the firewall. If your Jira is not behind firewall you can create account on our SaaS instance. In both cases reach out to us at [email protected]

What kind of user do I need to use/create to use during setting up the connection?

The user which has permission to the projects and items you want to synchronize. We do not require administrator permissions from the users as we are not performing any modifications in the app configuration.

What if we use another connection method than Basic Auth / OAuth?

There are many different authentication methods supported by the apps, e.g. Jira can be configured to use SSO. Please reach out to us at [email protected] to discuss opportunities.

Do we need to install anything in the app themselves (in Jira, in Snow, in Azure DevOps, etc.)?

Only for the Jira Cloud, we obligatory require to install one of our Jira Cloud apps, available on Atlassian Marketplace. For the Jira Server / DC it is not mandatory, reach out to us to discuss the licensing.
We do not require to install anything on Azure DevOps, Servicenow etc. (all other apps other than Jira) we are not requiring to install apps.

What are the main differences between SaaS and on-prem deployments?

Please read differences here On-Premise deployment
  • When your Jira Server / Jira Data Center is behind the firewall.
  • When your security policy requires you to have all the data stored in your company infrastructure
  • When you are going to synchronize a huge amount of items e.g. thousands of issues per day

How do getint work? Do you require to install the app?

Please read an overview here: Architecture

How to map task creation date?

Task creation date can not be mapped because it is calculated on creation by the app in which the item is created. Thus that you can not override that. Although, you can save the original creation date in a Custom Field. Reach out to us to learn how.

If I forget to map the status, will it error out? Will it skip? How the platform will behave?

It depends on the default mapping setting you have set up.

What will happen if my internet connection brake? Will I lose the data?

When can not connect with the apps during performing integration, because of e.g. no internet connection or the app is offline, it will fail to run and try again after a setup interval. It will again try to fetch items changed after a given time.

Is the application affecting Jira’s performance? is using the standard official REST API to communicate with the Jira. Jira is designed to handle a huge amount of REST API calls so it should not impact the performance. is designed to perform as least of requests as possible.
For Jira Data Center, you can also consider setting up a dedicated Node that will handle the REST API calls.

How often do you upgrade the app? How do I upgrade my on-premise application?

We release new versions at least once per month. Minor releases are done more often though.
To upgrade your on-premise version you can use provided scripts that you received during the installation process. You can read more on the Installation page.

What will happen if the API of the tool will changes? Will the platform stops working?

It should continue to work normally because the breaking API changes are introduced by apps/tools vendors very rarely. Although if something will be broken, you will start to see the errors. Reach out to us when this occurs.

What if I want to keep some comments private (and not being synced?)

There is a special option to filter out comments by visibility value.

Will I be notified if any error will occur?

We are not having this feature at the moment, but we plan to introduce it soon.

How can I monitor the On-Premise application?

The On-Premise version is a Java Sprint application using PostgreSQL and NGINX. Thus that it can be monitored using different monitoring applications.
We leave it up to customers to decide what monitoring tool suites them best. You can introduce some Application-level monitoring or Logs level monitoring as well because all logs are

If there will be an error, are there any logs to see what happened?

Yes, one of our biggest focuses was Reporting, providing as much as possible information regarding the performed synchronizations and collected errors, as possible. Thanks to this, we are able to solve most of the errors very very fast.

Can I provide the interval of the integration? Can it be real-time?

In the On-Premise version, you can provide 0s interval, which means that integration will start to sync changes immediately after its finish, so it can be almost real-time.

Is the performing one-way or two-way integration?

It handles both scenarios.

Can I move issues between the same Jira instances, just different projects?

Yes, definitely :)

How do I calculate the price of the app?

To calculate the price for Jira Cloud, use Atlassian's price calculator:
To calculate the price for Jira Server:
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Management (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Management, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
To get the price for Jira Data Center, reach out to us ([email protected]).
The price for integrations that do not include Jira, there is a flat price of $99.99/month.
In you pay for each connection (Jira-Asana is one connection, Asana-Service Now is another one).

How much time does it take to set up basic integration?

The setup of basic integration takes just about 3 minutes. This will let you sync the basic scope (title+description+attachments+comments). From that point, you can start working on more advanced cases to cover even very complicated cases.

Why I get 401 error when trying to UPDATE Jira Cloud app?

According to Atlassian recommendations for delivering Jira Cloud app, our Cloud apps are hosted on our servers and then served within iframes in a Jira Cloud to our customers. Whenever we have a new version, we are releasing it into our servers so the newest version is served to cloud customers. Thus that, there is no reason for customers to try to update to a new version, because they should be already on the newest one. We are responsible for updating cloud apps versions.