Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I would like to pull the resolution date (and resolution) for issues from the REST API. How can I do this? I have seen other questions about editing these fields, but I just want to read them. From what I've seen they are not technically "fields", and I don't see any examples in the documentation about how to get this information.
hi @djx
That could be a tricky one. To solve it with the least effort, I would propose.
Good Luck and let me know if you need further elaboration.
Cheers,
Karim
Hello @djx
In addition to @Karim ABO HASHISH 's suggested solution...
The record of an issue being completed / resolved / closed (whatever you want to call it) is recorded in the Issue's change log, which you can read via the Get changelogs endpoint.
Google 'jira cloud rest api closed date' to see where your question has been asked previously.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for this. I'm aware I can parse the data out from the ChangeLogs, but it seems strange that JIRA APIs don't consider it a field to be returned on the issue when it is stored directly on the issue in the database.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In Jira, there is more than one way for an issue to be considered complete / closed etc, which can also vary from project to project and issue type to issue type, so no singular field can ever be considered the source of truth.
Instead, the change logs are essentially saying "Whatever criteria you set for this issue type to reach what you said was the closed state for this project is recorded here".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You don't need any special implementation to get the resolved date.
In REST response, you can find field resolutiondate. This field has the same value as resolved.
I am not sure why it is named differently in UI and in REST response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could use the search endpoint and add the resolutiondate field:
${host}/rest/api/3/search?jql=issueKey%20in%20(${yourIssueKey})&fields=resolutiondate
Or if you're really adventurous, you could have a look at the calls in the Sprint Burndown report.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.