Common API to create JIRA ticket on both On premise and On Demand?

[AaRu]

Hi Team,

I'm planning to create integration with JIRA both OP(On-Premise) and OD(On-Demand),

So I would like to know the common flow of API to create a ticket in JIRA (in both)

Previously before the /rest/api/2/issue/createmeta deprecation i used the same for both OP and OD 

So kindly suggest some better flow for this common integration

Regards,

AaRu

[Milan Chheda [INFOSYSTA] · Accepted solution]

Hi @AaRu ,

Welcome to the community! 

Here are the API links that can help you to create issues: 

• https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-createmeta-get
• https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/
• https://developer.atlassian.com/server/jira/platform/jira-rest-api-example-create-issue-7897248/ 

Hope this helps you.

Thanks

[ServiceDesk Plus]

Yes we are also having similar Question but need common API for both OP and OD, 

But above mentioned API's cant be used in OD 

[AaRu]

Yes i read that but on demand JIRA doesn't support the below API's  

rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes

rest/api/2/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}

I m expecting the common API like "rest/api/2/issue/createmeta/ " which is used to be common for both OD and OP, but now its deprecated and will be removed later 9

[Milan Chheda [INFOSYSTA]]

Based on my knowledge, not sure though, the APIs won't be common for Cloud and Server. Any specific reason you want them to be same?
Also, what's the requirement or objective behind creating an issue in both JIRA environments?

[AaRu]

We developed integartion between JIRA and our application, Before deprecation of rest/api/2/issue/createmeta/ we have same API for both OP and OD , but now we are not having the same so need to know is there any common API 

[Milan Chheda [INFOSYSTA]]

So version 2 is latest for server while version 3 is in beta for cloud. As of now, version 2 is still available for cloud and you sure can have common API until version 2 gets deprecated. 

But I would recommend, if possible, to separate the logic because version numbers not necessarily would be same and also there are certain differences between server and cloud. Hence, better to have separate implementation and handle them individually than impacting both.