In a project moved from server to cloud, Resolution Date is not setting.

[Louise Baker]

We moved a project from jira server to jira cloud. Nearly everything is the same (afaict). However, when an issue is resolved, the resolution date is NOT automatically setting.

Is this an automation you need to create / build?

[Louise Baker]

I figured out my issue! Our workflow contained a screen displaying during a transition into "done", but this screen wasn't told to display in our Cloud instance. Therefore, developers were never prompted to set the resolution via a screen, and it wasn't able to be set via the ticket View, and Resolved never populated (because there was no resolution).

To play into the confusion, there was a custom field Resolution Date that was generated by a plug in at some point. It took a lot of unraveling but we've finally got it under control!

[Trudy Claspill]

Hello @Louise Baker 

What is the type of the project in Jira Cloud; Service, Software, or Business/Work Management?

For Business/Work Management projects, the Resolution and Resolved fields are not used.

[Bryan Trummer - ReleaseTEAM]

Hello @Louise Baker ,

It sounds like the workflow in the Jira server project was most likely setting the resolution, and it may not have moved over correctly in the Jira cloud version of the project. I would review the workflow for that project in both the Jira server and Jira cloud toward the final status to see if it was indeed being auto-set in the Jira server workflow or with a pop-up screen.

If so then you will want to update the workflow in Jira cloud.

If the workflows match in both instances and it's not setting the resolution you will want to check for any automation in the Jira server instance to see if that was resolving the ticket.