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.
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:
Components:
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!
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.
Please can you advise?
Best,
Andy
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.
Hey Zach,
Any news on fixing this issue??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does anybody know if competitors (status.io) support this function?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.