10 December 2019
Thank you for submitting a ticket with us.
You can set up an integration between HubSpot Tickets and Jira Issues with the help of Skyvia import packages.
However, since we are working with HubSpot and Jira through their APIs there are mandatory fields for mapping.
For Jira Issues for UPSERT operation among others the following fields are mandatory for mapping: Issuetype_Id, foreign ky from IssueTypes, Project_Id, foreign key from Project and Priority_Id, foreign key from Priority. In order to migrate records successfully, the data from these three related objects must be migrated prior to Issues integration and then it will be possible to configure a lookup, or the fields can be mapped with a constant that corresponds to appropriate values from Jira.
So, provided these objects are integrated and ready, you can set up an import package with HubSpot as a source and Jira as a target, map necessary fields and move data by schedule. There are no triggers in Skyvia but schedule can replace triggers in a certain way and run packages up to every minute.
For moving HubSpot ticket Id/URL to Jira a separate import package can be created.
There is no opportunity to "see" status updates/comments of one system in another one using Skyvia means.
For Tier 2 -> Tier 3 scenario one more import package or a separate task for second import package should be configured. It will have a filter by status or some other field that determines the difference between support levels.
Please note that Jira connector has some limitations in Skyvia. Please check them here.
More details about import package can be found here.
Feel free to contact us back, should you have any questions.