Resolve issues retrospectively

[Sayyed Shah]

Hi All,

We have a case where resolutions were not turned on and the team kept taking issues through different statuses and eventually marking them as done thinking that indicates the completion of the work. But when the team started looking into Jira reporting, they realized that all those issues are still open as far as Jira is concerned.

We have added the post function now to resolve the issues on a particular transition.

We can do a bulk update to mark the past issues as "resolved" but reporting wise that would indicate that all of those issues got resolved on the date of the bulk update.

Is there any way to apply, let's say the last modified date to resolutions?

Thank you

[Walter Buggenhout]

Hi @Sayyed Shah and welcome to the Community!

You are right about the reporting, but I would say: try not to bother. There are other places in Jira where reporting is based on other things - e.g. agile boards consider work as done based on when issues reach the rightmost column of your board, not based on the resolution being set.

Resolution date is a system date. It triggers when the field is set by the system and it is intentionally designed not to be manipulated. So just run the update; the spike in your reports will be there, but you can perfectly explain why this happened and what it meant.

Keep in mind that the tool is there to support you to deliver work, not to produce reports (whilst I do totally understand they help you understand your process). Just perform the update and take the learnings with you for the future would be my advice on this one.

Hope this helps!