It's not quite so simple to export this SLA data today. While you can display this data in the issue navigator of Jira, as you have noticed, when you export this the SLA data is not being included. There is an existing feature request for this in https://jira.atlassian.com/browse/JRASERVER-62457
I am speculating that the reason for this is that the SLA data doesn't appear in this CSV file is because it is much more complex to store these values in the database. SLAs are counting time values that are constantly changing. But these events are being stored in the "AO_54307E_SLAAUDITLOG" table of the Jira database.
But these are using a unix epoch time event field to store the specific time of the event, such as issue creation, completion, or breach of event, etc. I don't have a clear way to compute the values in this table to show this specific SLA metric into a CSV file. If you have someone that is very skilled in database administration, they might be able to make more sense of the data in those tables to create a script that might be able to display these data values.
However you might take a look at the Service Desk REST API on SLAs
https://docs.atlassian.com/jira-servicedesk/REST/3.6.2/#servicedeskapi/request/{issueIdOrKey}/sla-getSlaInformationById
It might be possible for you to create a script that could make a series of REST calls to the issues / SLA in question and grab that information into a json formatted file. I know this is not as simple as having a single CSV file with the data for each issue in Jira, but with the way the data is stored today, and the fact that the feature request does not appear to be coming any time in the near future right now, if you really need this data in that format, it is probably going to take some considerable scripting to accomplish.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.