Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Can you document an Incident after it happened in Jira with correct creation date and SLA? (Script)

msekyra
msekyra
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
December 12, 2017

Case: 

Incident happens on 30. Nov. 2 am. Solved at 3am. Not reported in Jira, not documented in Jira.

On 1.Dez we want to document it in Jira. It should be with Issue Creation Date 30.nov an with correct SLA.

Script:

We would like to solve it with Scriptrunner. Maybe a Post Function Script or with a Script Listener.

 

Do you know this case?

Which fields do we have to overwrite to display the correct data?

 

Thank You very much,

Cheers,

Michael

Answer
Watch
Like Be the first to like this
410 views

1 answer

0 votes
Ivan Tovbin
Ivan Tovbin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
December 18, 2017

For created and resolution dates I'd use setCreated(Timestamp created) and setResolutionDate(Timestamp resolutionDate) methods of the MutableIssue interface. 

As for SLA fields, I'm not so sure. Not very familliar with JSD Java API

Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Desk
Jira Service Management
TAGS
AUG Leaders

Atlassian Community Events

    See all events