Thank you @Heather Roberts

Hi 53842b4eba48, I have been discussing this with the engineers, and I think there was some confusion on that other support ticket (https://jira.atlassian.com/browse/JRACLOUD-80686), sorry about that.

For CMP projects, it depends entirely on what template has been used to create the project (eg. Project Management, Employee Onboarding). Only some project templates have the resolutions working by default (under the hood they are just automatically adding the post function to set/clear the resolution). The list of working templates are:

• Document approval
• Project management
• Task tracking
• Personal task tracker
• Go-to-market
• Process control

I have created a new support ticket (https://jira.atlassian.com/browse/JWMCLOUD-507) for us to add this behaviour by default to all CMP project templates, in the meantime the solution is to add the post function manually as it sounds like you have done.

Hi @Heather Roberts,
Actually we had to add a "Post Function" on the transitions in CMP projects to set or clear the resolution.

My understanding is that any transition to StatusCategory "Done" should set the resolution field, and any transition from StatusCategory "Done" to StatusCategory "To Do" or "In Progress" should clear it.

It was still not the case (confirmed by Jira support in https://jira.atlassian.com/browse/JRACLOUD-80686 ).

Hi 53842b4eba48, my understanding is that this was always working correctly for CMP, it was just in the TMP projects we had this bug.

You will no longer need any of the automation rules, moving issues from 'done' back to 'in progress' (or any non-done status category) will set the resolution as unresolved.

@Heather Robert, your colleague Anusha Rutman mentioned on JRACLOUD-80686 that this is also fixed for CMP.
Please confirm.

Also shall we keep the automation rule we had created for clearing the Resolution field if status changes back from "Done" or the fix was only for the one-way transition? 

This has been fixed and released to everyone Any issues moved to/from the 'done' status category from now on will have their resolution set correctly.

Something to note is that this will not be applied to historical data, any issues already in the 'done' category will not have their resolution automatically set to resolved. We were worried about the impact of making such a mass change to all projects' 'done' issues, so have left the decision to you if you wish to do a one-off update.

To do so, you can use Jira's bulk edit feature to update the resolution to 'resolved', you will only need to do this once, and any future updates will happen automatically. Follow the steps listed under the 2. Transition your issues heading here - https://confluence.atlassian.com/jirakb/bulk-update-the-resolution-field-in-jira-321857142.html#BulkupdatetheresolutionfieldinJira-2.TransitionyourIssues

Hi 137ca20adbf9, I understand it seems like a long time, the reason is the fix is rather complex and needs to be implemented by a Jira platform team that have many competing priorities, and we have agreed with them for an end of June timeframe. The good news is they are hopeful it will be done earlier, but as June was the agreed date this is what I am committing to on this ticket.

The suggested workarounds in the meantime are to either use an automation rule to set the resolution (mentioned in more detail in the description) or, depending on what kind of chart/graph you are building, to save a filter that retrieves the issues you need and use this in your chart.

Hi Heather Roberts, may we know why it takes that long for the thing to be fixed? Any suggested workaround where we can view the actual DONE and RESOLVED tickets with a corresponding chart or graph? Thanks!

Hi all! I am an engineering manager here at Atlassian and I am happy to say we have put this issue on our roadmap and will have the fix out to you before the end of June this year.

Why is it not a critical fix - virtually all reporting are useless!!!