Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,367,386
Community Members
 
Community Events
168
Community Groups

Is it possible to change incident status?

Is it possible to change incident status at creation time via API?

 

I'm trying to change the status at creation time, as every time I go to create the status is generated as "solved", and I want it to be created as "investigating".

 

Captura de Tela 2022-08-12 às 18.03.53.png Captura de Tela 2022-08-12 às 18.04.54.png

 

I'm already passing the status "investigating", but it doesn't solve.

Code:

 

{
"incident": {
"name": "[Teste]Nats",
"status": "investigating",
"impact_override": "none",
"scheduled_remind_prior": true,
"scheduled_auto_in_progress": true,
"scheduled_auto_completed": true,
"metadata": {},
"deliver_notifications": true,
"auto_transition_deliver_notifications_at_end": true,
"auto_transition_deliver_notifications_at_start": true,
"auto_transition_to_maintenance_state": true,
"auto_transition_to_operational_state": true,
"backfill_date": "string",
"backfilled": true,
"body": "string",
"components": {
"7yvk76r97rp0": "operational"
},
"component_ids": [
"f0vdktlv6y31"
],
"scheduled_auto_transition": true
}
}

1 answer

1 accepted

0 votes
Answer accepted
Arumugam M Atlassian Team Aug 17, 2022

Hey @Jonathan Brito

Good day! Hope you are doing well. 

This is Arumugam from Atlassian Support and I'm here to help!

I understand that you are creating incidents via API and you are running into an issue where the created incidents are in resolved status instead of Investigating

While looking at the payload that you shared above, it seems that you are sending the following key-value pairs which is the reason for this behaviour:

 

"backfill_date": "string",
"backfilled": true
Incident backfilling is something that you will need to pass if the incident is already resolved. 
If it is a new incident, please remove the above two values from the payload and try creating an incident, it should solve the issue. 
I hope this helps. Please let me know if you have any specific follow-up questions. 
Thanks, 
Arumugam

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events