Unrecognized field "released" in REST API

[Justin Israel]

We recently had an upgrade to Jira 8.1.0 and I am now finding that the versionmanager plugin fails when creating a new version, with:

JiraClientException: (500): <?xml version="1.0" encoding="UTF-8" standalone="yes"?><status><status-code>500</status-code><message>Unrecognized field "released" (Class jira.plugin.versionmanager.rest.bean.VersionBean), not marked as ignorable

I notice that when I get the GET versions results, it shows “status” field with an enum, and not any “released” bool. Is there an update to support the change or do I need to switch on Jira versions and use a POST that sets status=”Released” ? It looks like we have versionmanager 1.0, so maybe this is fixed in a newer version?

Thanks!

[Justin Israel]

I’ve fixed my issue by changing my request to set “status” to either “Released” or “Unreleased”. So I think really this ticket should just be about updating the Wiki REST api documentation to match the current options.

[Holger Schimanski]

Thank you very much for getting in contact. You are right, the REST API documentation needs an update.

Since version 1.2.0 of Version Manager for Jira you can set the status of a version to “Archived” in addition to “Unreleased” and “Released”. Therefor a change in the API was needed from boolean “released” to an enum “status”.

To change the 1.0 API without switching to 1.1 in the URL http://{YOUR_JIRA_HOME_URL}/rest/versionmanager/1.1/versionmanager/ was a follow-up mistake, but now I will not change it back to boolean and introduce a 1.1 REST URL because it is already released.