Div |
---|
|
On this page Table of Contents |
---|
maxLevel | 1 |
---|
type | flat |
---|
separator | pipe |
---|
|
|
Summary
SOAP to REST APIs
Many of Jira's remote APIs (SOAP APIs) that have been used historically in the Jira CLI will be removed from Jira 7.0. Replacement remote APIs (REST APIs) are available in Jira 7.0.
The Jira Server version of Jira 7.0 is expected to be released by Atlassian later this year. However, Jira Cloud has already been updated.
Little to no impact after both updates
This notice is let Jira CLI customers know that they will be able to move to Jira 7.0 with little or no impact, as our ongoing Jira CLI updates will adapt to the new interfaces under the covers. In fact, over the past years, some interfaces have already been converted to the new APIs or new functions have been implemented using the new APIs.
...
Table plus |
---|
|
Issue | Description | CLI Workaround | Customer Impact |
---|
ACJIRA-486 | Concurrency problems with project and issue related REST APIs. Tip |
---|
Resolved with Jira 7.2. Expected to be released on Cloud later in 2016. |
|
| - random errors when concurrent access occur (timing issue)
- unknown as to the extent of the problem
- unlikely in low use scenarios
- more likely in high activity, highly automated environments
| JRA-45371 | REST API issue metadata is not complete | some fields handled | - errors handling some custom fields
- CLI has special handling for some identified custom fields like Agile fields
- Open a CLI issue if you have a special case not covered
| ACJIRA-509 | REST API to retrieve comments does not respect maxResults or startAt parameters | | minor performance impact | ACJIRA-559 | REST API inconsistent error reporting for accessing project resources |
| minor | ACJIRA-487 | Incorrect editmeta for subtask - subtask issue types not in allowed values | | none | JRA-43695 | Workflow rest api - internal server error if workflowName is specified that does not exist | | none |
|
...