-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.1.8, 7.1.9
-
7.01
-
2
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
Unable to Release and Archive a version in a single REST call
Steps to Reproduce
- Create a version in JIRA
- Make sure this version is NOT released and NOT archived
- Referring to https://docs.atlassian.com/jira/REST/latest/#api/2/version-getVersion, run the following REST call using the PUT method with the below data: http://localhost:8080/jira/rest/api/2/version/10000
{ "self": "http://localhost:8080/jira/rest/api/2/version/10000", "id": "10000", "description": "An excellent version", "name": "New Version 1", "archived": true, "released": true, "releaseDate": "2010-07-06", "overdue": false, "projectId": 10000 }
Expected Results
- The details of the version is updated with the new values and is also Archived and Released
Actual Results
- The details of the version is updated with the new values but is only released. It is not being archived. The following is the response
{ "self": "http://localhost:8080/jira/rest/api/2/version/10000", "id": "10000", "description": "An excellent version", "name": "New Version 1", "archived": false, "released": true, "releaseDate": "2010-07-06", "userReleaseDate": "06/Jul/10", "projectId": 10000 }
- Running the same call again will archive the version
Notes
- The same happens when unreleasing and unarchiving in a single rest call
- The first call will unrelease it
- The second call will unarchive it
- Does not happen in JIRA 6.4.12
Workaround
Archive and Release the version in 2 separate REST calls
- relates to
-
JRACLOUD-61990 Unable to Release and Archive a Version in a single REST API Call
- Closed