-
Suggestion
-
Resolution: Timed out
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Thanks for trying out the new REST api!
With 4.2, we shipped an alpha release of our new REST API, which includes mostly read APIs for individual issues.
We continued to evolve the REST API in 4.3 and 4.4. We published the REST API documentation for 4.3 and 4.4 releases here:
In the JIRA 5.0 release we plan to take the JIRA REST API out of beta. As always, we would love to hear your feedback and comments about this feature. To keep the discussion centralized (both past and present), feel free to comment on this issue with your feedback.
Please note that the JIRA 5.0 version of the REST API has changed significantly from the alpha and beta API from previous releases. The JIRA 5.0 API goes well beyond the read-only API from previous versions. The new REST API should include create, update, delete, search for Issues and manipulation of individual issue fields.
- is related to
-
JRACLOUD-22093 Feedback for JIRA 4.2 beta
- Closed
-
JRACLOUD-24992 Add "su" functionality to REST API
- Closed
-
JRACLOUD-24994 Remove version from REST API URL
- Closed
-
JRACLOUD-25812 CLONE feature for REST API
- Closed
-
JRASERVER-22139 Feedback for REST API
- Closed
- relates to
-
JRACLOUD-25304 EAP Feedback - JIRA 5.0
- Closed
-
JRACLOUD-25596 Feedback for Java API
- Closed
-
JRACLOUD-26466 Improve JIRA REST API to allow users search for all issues connected to a version
- Closed