Tracking accurate SLAs on requests that are not logged immediately

I want to track SLAs (like time to first respone and time to resolution) but my service team may recieve requests via phone in some situation where the request can not be logged to the JIRA Service Desk system immediately. I want to either change the date/time that the issue is created to reflect when the incident was truly discovered OR have separate custom fields to track this and use these to measure SLAs.

Is there:

a) any way to create an issue and then change the creation date?

or b) use a custom field, e.g. detection date/time to track start time and another field, e.g. response time, to end the SLA


1 answer

SLAs are based on events, not field values. I think the easiest thing would be to use a CSV import to update issues at the end of the day:

Or you could have staff just log everything in a CSV and then import that at the end of the day. Whichever is easier for you.

Hi, link doesn't work. Thanks for your help. I think this defeats the purpose of having JIRA! If we can't log everything easily via the webapp

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,409 views 15 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you