Open aculpepp opened 1 year ago
Quickly comparing API documentation for Jira Data Center vs current code base, endpoints seem to be the similar to both Jira Versions, the difference is we'd have an "url" custom field for the Server or Data Center, and for Jira Cloud we add an additional CoudId.
Structure of API URLs in Jira DAC is:
http://host:port/context/rest/api-name/api-version/resource-name
i,e,
https://jira.atlassian.com/rest/api/latest/issue/JRA-9
now taking a look at the code base for Jira Cloud components at PD repo:
_getUrl(cloudId) {
return `https://api.atlassian.com/ex/jira/${cloudId}/rest/api/3`;
},
from addComment to Issue
method: "POST",
path: `/issue/${issueIdOrKey}/comment`,
...args,
so final API url for Add Issue to comment https://api.atlassian.com/ex/jira/{your_coud_id}/rest/api/3/issue/{your_issue_id_or_key}/comment
_Perhaps it can easily be abstracted out the code to be shared by both Jira Cloud and Server/Data Center components, or Server/Data Center be built easily from Cloud components (and maybe have the user test Server components
Would like to request support for Jira Server/Data Center. Currently only Atlassian cloud is available.
Name of app / service Jira Data Center
Link to developer documentation
Is lack of support preventing you from building workflows, or do you have a workaround? We cannot use the tool at all due to not supporting Jira Data Center version. We run our Jira in AWS so its still cloud based.
Are there specific actions, or triggers, you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each! Mimic what is available in Jira Cloud (Atlassian)