WHY I CANNOT FIND CLOSED DATE ? LIKE CREATED AND ALL..

[FARAH BAL]

I need to generate the report and i couldnt find the closed date. But Created/Updated is there... but not Closed Data. Anyone can help?

[Nic Brough -Adaptavist-]

Created and updated are system fields that are calculated for you.

"Date closed" cannot be, as Jira does not know what you might consider to be the date an issue was closed - that depends on your process and workflow.

If you want to see your version of closed date, you'll need to capture it as part of your workflow, then you'll be able to include and show it in reports.

The other option is to work with Jira's default assumption of when an issue is closed, which Sachin mentioned already.  That is "whenever the resolution last changed to a value other than null".  This is captured in the field called simply resolved , so if that measure would work, try adding that to the reporting.

[rklarr]

How is the date when the status was changed to "Done" or "Complete" not recognizable as "closed"??  For a simple helpdesk ticketing system, the "resolved" field is redundant. 

So now I guess I'm adding "Resolved" to my workflow and looking for a way to mass change all "Done" or "Complete" statuses to "Resolved" so I can report on "Closed" tickets. Super. 

[Sachin]

hello @FARAH BAL , Jira considers an issue as closed when the "Resolution" field has a value. You can use one of the below examples which will give you the results you are looking for -

• Find all issues that were resolved before 31st December 2010:
  resolved <= "2010/12/31"
• Find all issues that were resolved before 2.00pm on 31st December 2010:
  resolved < "2010/12/31 14:00"
• Find all issues that were resolved on or before 31st December 2010:
  resolved <= "2011/01/01"
• Find issues that were resolved in January 2011:
  resolved > "2011/01/01" and resolved < "2011/02/01"
• Find issues that were resolved on 15 January 2011:
  resolved > "2011/01/15" and resolved < "2011/01/16"
• Find issues that were resolved in the last hour:
  resolved > -1h
  
  -SLA: Search for requests whose SLAs are in a certain-
  

• Find issues where Time to First Response was breached:
  "Time to First Response" = everBreached()

• Find issues where the SLA for Time to Resolution is paused due to a condition:
  "Time to Resolution" = paused()

• Find issues where the SLA for Time to Resolution is paused due to the SLA calendar:
  "Time to Resolution" = withinCalendarHours()

• Find issues that have been waiting for a response for more than 1 hour:
  "Time to First Response" > elapsed("1h")

• Find issues that that will breach Time to First Response in the next two hours:
"Time to First Response" < remaining("2h")

•  

[FARAH BAL]

hi Sachin. I am sorry, but i need the closed date on this. when i export, there is no closed date. why ya? because i need to generate report which is includes closed date.

[FARAH BAL]

okay, i need to go to column there which type of things i want it to come out as output. but i couldnt find closed date...

[Rolf Breuer]

I totally agree.  They want to impose their process on us.  And we all have different ones.  I wonder sometimes whether they actually listen to us - THE CUSTOMER/USER?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

They don't want to have to guess at and then provide for every possible customers.

You can add your own custom date fields, and do with them what you want.

[FARAH BAL]

And also i couldnt find total resolved time. Anyone please help me :(