That's not quite true - resolution date is not always closed date.
The answer to the question givein is simply "look in the issue history", but I suspect there's a further question, in that the poster will want to report on the date directly (for example "closed date < -7d"). JQL doesn't let you interrogate the history quite that easily, and most places won't display the date either (the issue navigator only displays fields, not "stuff we extracted from the history").
To solve this problem in the future, the most easy option is to add a "closed date" date/time field and use a plugin to give a transition post-function that sets this date to "now" when any close transition is used.
Thanks Nic. You are correct. I know where to find dates in issues and I know how to do advanced queries. However, there is no Closed date anywhere that I can query on that I can find and you have confirmed that. I will look to the transition post-function as a solution. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Andrey's plugin is nice. You can also createcustom field called Script Field with Scriptrunner plugin to get this information automatically.
Link to documentation how to create Script field:
https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+Fields?src=contextnavchildmode
Code for this Script Field:
import com.atlassian.jira.ComponentManager def componentManager = ComponentManager.getInstance() def changeHistoryManager = componentManager.getChangeHistoryManager() changeHistoryManager.getChangeItemsForField(issue, "status").find {it.toString == "Closed"}?.getCreated()
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What if the issue gone through a cycle and closed multiple times? What would this scripted field return?
The first time the issue was closed? Or the last time?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As Royce pointed out above...
Does anyone know how to use this logic similarly to get the LAST time the issue was Closed - in case it was allowed to Close multiple times?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can find here: https://marketplace.atlassian.com/plugins/ru.andreymarkelov.atlas.plugins.datacollector
in issue tabs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I want to Get Closed Date from script runner with below script. It works but not exact due to Timezone difference. How can I get exact date?
import com.atlassian.jira.ComponentManager
def componentManager = ComponentManager.getInstance()
def changeHistoryManager = componentManager.getChangeHistoryManager()
changeHistoryManager.getChangeItemsForField(issue, "status").find {it.toString == "Closed"}?.getCreated().format('dd/MMM/yy HH:mm')
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's the date it was closed... the server date is authoritative. You can adjust it for display to clients, but you haven't given any context so don't know what the circumstance is.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jamie Two users - User1 at Time Zone: (GMT+05:45).This is set in user profile. User2 at Time Zone: (GMT-06:00).This is set in user profile. System/apps hosted in Time Zone: (GMT-06:00) getCreated() gives the date at Time Zone: (GMT-06:00). So User2 has no problem. But the user1 gets the date of (GMT-06:00). Whereas other dates like Resolved, Created , updated are in (GMT+05:45). I want to get Closed date in (GMT+05:45) for User1. I want generic solution that can work for any users in any Timezone.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Susan
You can find this information inside the issue at the right corner at the resolution date.
Hope it helps,
Ricardo Carracedo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.