JIRA Documentation

JIRA 6.4.x
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

Symptoms

After resolving and reopening a ticket, you realize that the initial resolution date has been updated. The only way to see when this was first resolved is by accessing the history tab in your issue. 

Cause

The Resolution timestamp is automatically updated when there is an update to the Resolution field.

Workaround

  1. Install JIRA Suite Utilities so that we have access to the extra conditions and post functions we need for your workflow.
    1. JIRA Cloud Instances can Enable the JIRA Suite Utilities by going to JIRA AdministrationAdd-onsManage Add-ons > search for "JIRA Suite Utilities" and click Enable (keyboard shortcut: g+g > Manage Add-ons)
  2. Create a new Custom Field using the "Text Field (single line)" option, we called this "First Resolution Date," and make sure it is on the appropriate screens. Ideally we would want to use a Date/Time field, but it seems that JIRA Suite utilities is not able to condition on date fields at this time.
  3. Copy and Edit your Workflow and create a New Transition that is basically the "Resolve Issue" transition but has a condition that checks to make sure that "First Resolution Date" field is null.  This will ensure that this transition only shows up when the First Resolution Date has not already been set. 
    1.  The New Transition name cannot have the same name as another Transition
    2. For Example: if your "Resolve" Transition is between "In Progress > Done," create a new "Resolve Issue" Transition along the same "In Progress > Done" path
  4. Once the condition is set, then create a post function for this transition that updates "First Resolution Date" to grab the current time (variable: %%CURRENT_DATETIME%%).  
  5. Update the "Fire a Generic Event event that can be processed by the listeners." Post Function to be the Issue Resolved event instead (this should ensure that the Resolution date field is updated as well).

Related Content

 Expand to see related content

Help us improve!

Is this article helpful?
Is the content complete?
Is it well written?

  • No labels

3 Comments

  1. The cause is when the Resolution is updated, not the Status

    1. Fixed. Thanks for verification Matt.

  2. Hi,

    This information is really helpfull. Someone knows if Atlassian has in his backlog an improvement that makes viable to use the date field instead of the text field?

    Thanks!