Can't create synchronisation task (MS SQL db and Jira Service Management)

  • 26Views
  • Last Post 08 December 2022
  • Topic Is Solved
0
votes
Thomas Balasch posted this 29 November 2022

Dear support team,

we are currently testing Skyvia for transferring/synchronising data between our selfhosted MS SQL data base and the Atlassian Cloud (Jira Service Management).

When I try to set up a synchronisation package and create a task, I am able to select the tabel from the MS SQL data basa (self hosted with agent connection). On the JSM side I can't select or search anything.

Also alll connection are tested successfully.

I hope you can help us?

Best regards,

Thomas Balasch

Attached Files

Order By: Standard | Newest | Votes
0
votes
Mariia Zaharova posted this 30 November 2022

Hello Thomas,

 

Thank you for contacting us.

 

Skyvia does not support Synchronization for Jira Service Management since none of the objects has the UpdatedDate field.

See more here https://docs.skyvia.com/connectors/cloud-sources/jiraservicemanagement_connections.html

 

Best regards,

Mariia

0
votes
Thomas Balasch posted this 01 December 2022

Hello Mariia,

thank you for the feedback.

I'm afraid I overlooked that, sorry about that.

So just out of curiosity...Requests in Jira store an updated time and date field, but the associated object doesn't provide that?

I am asking because in our use case we first create a Jira request from a set of data (request inside SAP) from a dedicated data base using Skyvia. From there on we want to keep the data (inside the data base between Jira - SAP) up to date, even if changes are initiated in Jira at some point.

Thank you and best regards,

Thomas

0
votes
Mariia Zaharova posted this 02 December 2022

Hello Thomas,

 

We are working with Jira Service Management via its REST API. None of the objects has the UpdatedDate field that is usually used to store records modification time and must be used in the Skyvia synchronization package. So this is a Jira Service Management REST API peculiarity. Here is an example of the Customers and Organizations tables:

https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-customer/#api-rest-servicedeskapi-customer-post

https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-organization/#api-rest-servicedeskapi-organization-get

 

Just for example, here is the link to Jira Issues API. The Issues table has both updated/created fields.

 

Best regards,

Mariia

0
votes
Thomas Balasch posted this 06 December 2022

 Hello Mariia,

thank you for the explanation. This was very helpful as it clarifies the current limitations of the Atlassian REST API.

So the Jira Issues API is also not usable for synchonisation packages even tho it provides updated/created fields if I understodd correctly? 

Sorry for so many questions, just trying to understand everything as good as possible as this a very high profile use case for us.

Thank you and best regards,

Thomas

0
votes
Mariia Zaharova posted this 07 December 2022

Hello Thomas,

 

Thank you for your reply.

In the case of using the Jira connector (not a Jira Service Management one), the Issues table can be used in Synchronization packages.

See more here https://docs.skyvia.com/connectors/cloud-sources/jira_connections.html

 

Best regards,

Mariia

0
votes
Thomas Balasch posted this 07 December 2022

 Hello Mariia,

thank you for clarifying this again. I wasn't aware that it made a difference if the issue is part of a JSM oder Software project.

Best regards,

Thomas

0
votes
Mariia Zaharova posted this 08 December 2022

Hi Thomas,

 

You are welcome!

 

Feel free to ask any further questions.

 

Best regards,

Mariia

Close