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,369,309
Community Members
 
Community Events
168
Community Groups

Unable to backfill incidents by component to calculate uptime

I'm trying to backfill past incidents to calculate 90 day uptime by component.

I am going to 'Create Incident' > check 'Backfill an incident that happened in the past' > enter 'Incident Start Date'.

However, there is no place to enter a date in which the incident was resolved. And there is no way to check which components were affected.

4 answers

1 accepted

3 votes
Answer accepted
Zach Atlassian Team Oct 13, 2020

Hey Khoi

While there isn't any functionality within the application to backfill component downtime while backfilling an incident, there is actually a way that you can backfill the data but it would actually be in a different process. The backfill incident tool itself is meant to point out incidents but those are not editable. Here is what you can do to accomplish the goal you are looking for. I have broken it into two separate sections since incidents and components need to be edited separately for this scenario.

Incident backfill:

  1. Create a new incident and make sure the notifications are turned off so subscribers aren't confused about the incident. I would leave the messaging on the incident as TEST to make it clear that it isn't a brand new incident (you can edit this later). It's also important to add any components related to the incident but make sure you leave them as functional since they aren't broken right now.
  2. After the incident is created, immediately resolve the incident, again making sure notifications are off and to use language not intended to cause confusion.
  3. Once it has been resolved, go into the incidents section and edit this incident. You can do this by clicking on the pencil icon that appears when you hover over an incident. From here you can change the dates and times on these, as well as edit the text to reflect the actual incident. After that has been set, you can move on to your components.

Components:

  1. Navigate to the components section, find the component and click on edit
  2. Find the Uptime History and click on the box for the day you wish to edit (please note that this section needs to be enabled to edit the history)
  3. On the pop up that appears, enter in the amount of time that the component was down as either a total outage or a partial outage (whichever is applicable).

If you happened to select a component when you created the incident, you will now see the related incident on the uptime tracker when you hover over that particular day.

I know this seems like a bit much but this is would be the best way to do this as the backfill tool can't get that detailed. Please let me know if you have any other questions, otherwise, I hope you have a great day!

Thanks! This should work for us. I'll try it out.

Hi @Zach

 

I have followed your instructions but the

"If you happened to select a component when you created the incident, you will now see the related incident on the uptime tracker when you hover over that particular day"

part is not working as demonstrated in the following screenshot.

 

Screenshot_23_03_2021__10_00.png

Please can you advise?

Best,

Andy

Same here, we can not adjust things retrospectively

Hey Zach,

Any news on fixing this issue??

Does anybody know if competitors (status.io) support this function?

hi Atlassian team, any updates on the above? the suggested workaround doesn't work, as the affected time by component is not being updated retrospectively. Thanks  

Hello Atalssian team. 

Is there some plan to improve this experience in the future? We have been considering StatusPage but the workaround seems time-consuming as well as potentially dangerous if during any of future backfills we forget to remove notifications to customers who are subscribed for updates. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events