It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Set ResolutionDate Programmatically? Edited

I wanted to change the closed status of a project's issues from A -> B, but made a mistake where I wiped out all of the resolutions that were set (on 1900+ issues). I know the mistake made, but now to recover the best I can. 

Initially, I wrote a Jira Python script that will iterate over all affected issues, search each issue's history to find the resolution it had before "the great wiping" this afternoon, then use update to set the issue's resolution to what it was most recently. After running this on about 50 test issues, I noticed there was a problem: the test issues have their nicely reset resolution set, but no resolutiondate field set.

I went back into jirashell to try to figure out how to set the resolutiondate, but no luck:

text: Field 'resolutiondate' cannot be set. It is not on the appropriate screen, or unknown.

Searching around, it seems that I might not be able to do it with a simple Jira Python script. (Well, maybe I could if I combine it with a connection directly to the Jira database to feed it SQL updates based on the history.created value of the appropriate history item, but that feels like it might be removing one too many safeties.) 

I suspect I'll have some success if I transition the affected issues from B -> B and setting the resolution in the transition, but I'd like to avoid putting them through another transition again. 

Any suggestions? Should I suck it up and go down the reflexive transition path or would there be another way to recover these resolutions and resolutiondates? 

(This is for Jira 7.9.0, not the version I mistakenly gave on the right and now can't edit.)

1 answer

1 accepted

1 vote
Answer accepted
Hana Kučerová Community Leader Aug 01, 2020

Hi @PeteToscano ,

this is a little bit strange, I believe the resolution date should be set automatically, when the resolution is set.

ScriptRunner for Jira has the Built-in Script, which is called Bulk Fix Resolutions. Maybe you can try it, if the behaviour would be the same or not.


Thank you for the response. I did try the Bulk Fix Resolutions built-in script, but it didn't set the resolution date either (despite what the documentation said).

That said, I ScriptRunner for Jira did help me solve this issue. I took some responses from here and combined them with pieces from the Adaptavist Library and came up with a script that'll do what I was looking for. 

(Yes, this is ugly code with lots of room to improve, but it seems to have worked. It's the first time I've played with Groovy. I'm tired, but I wanted to give back.)

This script will iterate over all issues returned by a JQL query and, for each issue, it will use the first resolution-related history item to determine the "real" resolution and timestamp to use. It'll then save the updated issue and reindex it. I hope this is helpful for someone else.

EDIT: Added description of what this script does.

EDIT2: Edited the EDIT. :D 

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.web.bean.PagerFilter
import org.apache.log4j.Level
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.history.ChangeItemBean
import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.issue.IssueFactory
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.index.IssueIndexingService
import com.atlassian.jira.util.ImportUtils

def changeHistoryManager = ComponentAccessor.changeHistoryManager

// Set log level to INFO

// The JQL query you want to search with
final jqlSearch = "status = closed AND project = FOO AND resolution is not EMPTY AND resolutiondate is EMPTY"

// Some components
def user = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def searchService = ComponentAccessor.getComponentOfType(SearchService)

// Parse the query
def parseResult = searchService.parseQuery(user, jqlSearch)
if (!parseResult.isValid()) {
log.error('Invalid query')
return null

def indexingService = ComponentAccessor.getOSGiComponentInstanceOfType(IssueIndexingService)

try {
// Perform the query to get the issues
def results =, parseResult.query, PagerFilter.unlimitedFilter)
def issues = results.issues
issues.each {
MutableIssue miss = ComponentAccessor.getIssueManager().getIssueObject(it.getKey())
def changeItems = changeHistoryManager.getChangeItemsForField(miss,"resolution")
for (item in changeItems) {"Time: " + item.created + "\tFrom: " + item.fromString + "\tTo: " + item.toString)
boolean wasIndexing = ImportUtils.isIndexIssues()
} catch (SearchException e) {

 Thanks again,


Like Stan Surin likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you