Transition issue with optional resolution fails via REST

Marius Shekow

I'm using the Atlassian C# SDK (which uses REST under the hood). I would like to transition an issue into the "Resolved/Closed" state. This does work on some Jira servers, but on one specific Jira server (v8.20.20) it does not.

The error message is: Field 'resolution' cannot be set. It is not on the appropriate screen, or unknown.

Code:

 

var resolutions = await jiraClient.Resolutions.GetResolutionsAsync(); // to determine the resolution ID
var testIssue = await jiraClient.Issues.GetIssueAsync("FOO-1234");
testIssue.Resolution = new IssueResolution("some-valid-resolution-id");
var available = await testIssue.GetAvailableActionsAsync(); // to get the transition ID
await testIssue.WorkflowTransitionAsync(some-valid-transition-id);
/*
Makes REST Call (POST) to http:.../rest/api/2/issue/FOO-1234/transitions
{
  "transition": {
    "id": "some-id"
  },
  "fields": {
    "resolution": {
      "name": "Done",
      "id": "10000"
    }
  }
}
*/

 

Closing the issue on Jira's web interface works fine. What's weird is that the web-tools of the browser tell me that the Resolution field shown in the web form is a (non-mandatory) field named

customfield_11338 which is not listed when I call http://.../rest/api/2/issue/createmeta?expand=projects.issuetypes.fields&projectKeys=FOO&issuetypeIds=<my-issue-type-id> or http://.../rest/api/2/issue/FOO-1234/editmeta

Any advice?

Florian Bonniec

Hi @Marius Shekow 

Resolution is mandatory as long as it's in the transition screen. If it's not it's not mandatory. If you try to set the resolution it has to be in the transition screen. So I guess the resolution is not set using the web UI, or if there is any value it's set using a post function.

 

You should not include the resolution if set using the postfunction or add the resolution field in the transition field of the transition you trigger

 

Regards