-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Update 13 Jan 2016: JIRA Service Desk now has a public REST API. See comment below.
As outlined in this answer question https://answers.atlassian.com/questions/225223/does-jira-service-desk-have-a-public-rest-api# JIRA Servicve Desk does not currently have a public REST API.
We do have internal REST resources that we use in the agent view and we plan to expand that into the "customer portal view" soon but these do not have the strong API guarantee against change. They are there to support the "dynamic browser front end".
Service Desk is of course built on top of the JIRA platform so issue creation / retrieval REST APIs are available via standard JIRA facilities.
https://docs.atlassian.com/jira/REST/latest/
As the JIRA Service Desk architect I am intrigued to learn more about about what type of REST APIs people would like and what use cases you are trying to satisfy and how they are more specific to JIRA Service Desk than the current JIRA public REST api.
Please use this improvement request on JAC (https://jira.atlassian.com/) or send me a direct email on brad.baker@atlassian.com to further discuss what you are after.
- incorporates
-
JSDSERVER-346 SLA Fields' values are not return correctly in JIRA rest
-
- Closed
-
-
DESK-2343 Failed to load
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
-
TESLA-586 Loading...
- relates to
-
-
- Closed
-
-
- Closed
-
- Closed
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-107] Create a public REST API for JIRA Service Desk
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 110459 ] |
| Workflow | Original: JAC Suggestion Workflow [ 3012925 ] | New: JAC Suggestion Workflow 3 [ 3649967 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2663557 ] | New: JAC Suggestion Workflow [ 3012925 ] |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2324365 ] | New: Confluence Workflow - Public Facing v4 [ 2663557 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JSD Suggestion Workflow [ 2053399 ] | New: JSD Suggestion Workflow - TEMP [ 2324365 ] |
| Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048493 ] | New: JSD Suggestion Workflow [ 2053399 ] |
| Workflow | Original: JSD Suggestion Workflow [ 1280277 ] | New: JSD Suggestion Workflow - TEMP [ 2048493 ] |
| Description |
Original:
(i) _*Update 13 Jan 2016: JIRA Service Desk now has a public REST API. See [comment below|https://jira.atlassian.com/browse/JSD-107?focusedCommentId=853509&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-853509].*_
As outlined in this answer question https://answers.atlassian.com/questions/225223/does-jira-service-desk-have-a-public-rest-api# JIRA Servicve Desk does not currently have a public REST API. We do have internal REST resources that we use in the agent view and we plan to expand that into the "customer portal view" soon but these do not have the strong API guarantee against change. They are there to support the "dynamic browser front end". Service Desk is of course built on top of the JIRA platform so issue creation / retrieval REST APIs are available via standard JIRA facilities. https://docs.atlassian.com/jira/REST/latest/ As the JIRA Service Desk architect I am intrigued to learn more about about what type of REST APIs people would like and what use cases you are trying to satisfy and how they are more specific to JIRA Service Desk than the current JIRA public REST api. Please use this improvement request on JAC (https://jira.atlassian.com/) or send me a direct email on brad.baker@atlassian.com to further discuss what you are after. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-107]. {panel} (i) _*Update 13 Jan 2016: JIRA Service Desk now has a public REST API. See [comment below|https://jira.atlassian.com/browse/JSD-107?focusedCommentId=853509&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-853509].*_ As outlined in this answer question https://answers.atlassian.com/questions/225223/does-jira-service-desk-have-a-public-rest-api# JIRA Servicve Desk does not currently have a public REST API. We do have internal REST resources that we use in the agent view and we plan to expand that into the "customer portal view" soon but these do not have the strong API guarantee against change. They are there to support the "dynamic browser front end". Service Desk is of course built on top of the JIRA platform so issue creation / retrieval REST APIs are available via standard JIRA facilities. https://docs.atlassian.com/jira/REST/latest/ As the JIRA Service Desk architect I am intrigued to learn more about about what type of REST APIs people would like and what use cases you are trying to satisfy and how they are more specific to JIRA Service Desk than the current JIRA public REST api. Please use this improvement request on JAC (https://jira.atlassian.com/) or send me a direct email on brad.baker@atlassian.com to further discuss what you are after. |
| Link |
New:
This issue relates to |
| Labels | Original: affects-cloud sdt | New: affects-cloud affects-server sdt |