You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is there any difference between PUT and PATCH requests for /pages/{page_id}/incidents/{incident_id} URL to update an incident? I see same result using any of the above,
@Sandeep_A Welcome to the community!
There is slight difference here (https://developer.statuspage.io/#section/Basics)
This means that when you call PATCH on `Incident`, only field that you are passing as payload will be updated and rest will remain same.
With PUT, all fields will be updated (i.e. old field will be replaced), it will require to send all fields as payload.
As an example, I am trying to update a particular component associated with an incident with PATCH request as below. As a result of this request, the other components associated with this incident are removed and only the one in the request is present. Ideally, the PATCH request should have just updated the component listed in this request and leave the rest as is. Any thoughts ?
{
"incident": {
"name": "Sample incident modified",
"status": "monitoring",
"impact_override": "minor",
"body": "We are continuing to work on a fix for this issue. Monitoring",
"components": {
"2vjjt397ssd2": "operational"
},
"component_ids": [
"2vjjt397ssd2"
]
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sandeep_ABy general API conventions your assumption is correct, but not all API providers are equal. So I guess for Atlassian in case of StatusPage, you need to provide full set for 'components_ids'.
But I will check with Atlassian team, if this is a design bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure Thanks!. For now, there is no difference in the way PUT and PATCH behaves for this end-point.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello. I am on the exact same situation. When i try to add a new component in the components_id the previous values are replaced.
So the only solution is to populate again the 2 arrays
components and
component_ids??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.