As @Nic Brough -Adaptavist- says the resolution is set. Here is some guidelines for the resolution field
Resolution Field
Resolution Field can't be made optional. DO NOT put the field on any screen except the one presented in the transition where it is to be set. Resolution is a special field in JIRA. It has an initial value of ‘Unresolved’, which means the field is NULL in the database. It is ALWAYS required when it appears on the screen. ONLY display it on the screen during a transition to the status where you want it set. Once it is set the issue ID will appear with as strikethrough. If you re-open an issue the transition from closed to reopen needs to have a post function to CLEAR the resolution field to set it back to Unresolved.
Limiting resolution options
Use the jira.field.resolution.include workflow property
for exampl jira.field.resolution.include =1,2,3 where 1,2,3 are the resolution ids
https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html
Done status showing Unresolved
This is a problem that seems to be cropping up of late. Issues need to have a resolution set. Unresolved means the resolution field is NULL in the database. This means the workflow isn't providing for setting the resolution before going to the status flagged as Done. You need to fix the workflow.
The transition moving to ‘Done’ needs to one of two things; 1. Present a screen where the user sets the resolution or 2. Sets the resolution in a post function.
To correct the existing issues you can add a transition from the done status back to itself with a transition screen to set the resolution or a post function to set it. The other option is to add the resolution field to the edit screen (which you should NEVER do in production), bulk edit the issues to set the field and then REMOVE the resolution field form the edit screen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.