Hi 703b3e3aec21 thank you for your feedback! I discussed the points you have raised with the engineers who confirmed that the problem (and fix) is the same for company-managed and team-managed Jira Work Management projects so two separate issues are not required.

I have also added a note about the impact on reports to the description of  JWMCLOUD-180 – TMP Resolution field does not change to resolve when issue move to done. This problem would also be addressed by the same fix.

With this in mind, I will close this ticket and move any internal ticket references to JWMCLOUD-180.

In my opinion, this is not a duplicate of JWMCLOUD-180. 

That issue is specifically about Team Managed projects.

This issue applies to both Team Managed and Company Managed projects.

Also, that issue doesn't note that this problem makes the Created vs. Resolved report, available in the Reports section of a Work Management project, useless. Is that impact noted elsewhere as a separate issue to resolve, and linked to the issues about the setting of the Resolution field?

As 03c822d7804d noted, I believe this issue is a duplicate of JWMCLOUD-180 – TMP Resolution field does not change to resolve when issue move to done

I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!

This appears to be closely related, if not a duplicate of https://jira.atlassian.com/browse/JWMCLOUD-180.

The Created vs. Resolved and Created Issues reports built into the template will not reflect resolved issues because no resolution is set, and there is no option to do so aside from automation.