Is there an API to get a close date of an issue.?

[Rupal Khare]

I want to track and log the date on which issues are being closed, Is there any API i can use?

[Ronald Vallenduuk]

There is no direct closed date field on the issue, but you can find it in the issue history or changelog as described here:

https://community.atlassian.com/t5/Jira-questions/Issue-history-through-REST-API/qaq-p/503830

[Petter Gonçalves]

Hello Rupal,

The closure date of an issue would be registered in the resolution date field, considering that a resolution is set once the issue is closed.

That been said, the following query should return the Resolution date of a specific issue:

https://yourdomain.atlassian.net/rest/api/3/issue/issuekey?fields=resolutiondate

Where the issuekey parameter of the URL must be replaced with the issue key you want to return.

For more information about this, check the documentation below:

- Get Issue - REST API

Let me know if you still have any questions.

[Ronald Vallenduuk]

This is based on the (false) assumption 'that a resolution is set once the issue is closed'.

In our workflows resolution is set after QA, the issue doesn't get closed until after UAT.

See below for correct answer.

[Petter Gonçalves]

Hello @Ronald Vallenduuk

Thank you for your feedback.

Actually, the resolution field was designed to be added once the issue is completely closed/resolved. In fact, the goal of using the resolution field would be to specify the reason an issue is closed and removes the need of having multiple statuses with the purpose of stating why the issue is closed, as you can see in the KB below:

Best practices on using the "Resolution" field 

Although you can add the resolution before the "Done" status of your workflow, your issues will be considered closed in Jira application, so several reports and system filters will not work as expected (As you can see in this example). 

Basically, your issues will not be tracked and the progress/estimation of your (still) open issues will not be considered, causing unexpected behaviors if you want to use the full functionality of Jira Cloud as it was designed to work.

Please, take a look at the mentioned KB and let us know if you have any questions.