How to indicate affected components when backfilling an incident
Asked by Jeremy Goldsmith:

I have to backfill an incident and have filled in the description, but I see no way to indicate which components were affected. As we have an Access Control package, allowing clients in each shard only to view their own components, anything I add without indicating a component will be invisible to everyone.

Is this accurate, or is there a way for me to do this so that it shows up for the one affected shard? Currently I suspect that I cannot effectively backfill anything as nothing will show up for our clients in the affected shard.

If that is accurate, is there any way to make a feature suggestion that we are able to set the affected components?


Answers:
author: Nick Cruickshank
body: Hi

As far as I am aware, you would need to go to each affect component and on the uptime graph, select the day and update if there was a partial or major outage and the length of time.

I hope this helps.

Regards,

Nick

comments: author: Jeremy Goldsmith
body: Top moves, Nick; thank you very much!


author: vishal.shah
body: but this doesn't help completely. Since on the status page when you hover over the affected day, it shows the downtime but says no associated incident tied to it. how to you link the historical manually entered incident to the manually edited component down time


author: Jeremy Goldsmith
body: Agreed. I think this is not possible and is a missing part of the functionality. I have been unable to find anything to suggest that this can be done and even the suggested answer above goes less than half way to achieving the obvious desired outcome.

From my perspective, it's even worse than you described as the historically entered incident is invisible to our clients on the affected shard, since they can only see things related to their shard and it can't be tied to any when adding historically. The result is an orphaned description which only my team can see (utterly useless) and recorded degradation time with no corresponding incident as far as our clients can see.


author: Nick Cruickshank
body: I do not think degraded performance shows as downtime on the components only outages, however, yes when you backfil an incident there should be functionality in place that updates the component view to show outages.


author: Ilyas M
body: Hi, i also think, that to choose an affected component is a missing function when backfilling an incident. How can i suggest to implement this feature?


author: Yuri Bushnev
body: Yes, it is very confusing and seems like a miss of obvious critical capability. Quite sad, we continue to find more and more critical limitations for the StatusPage product every day.


author: John Hellenberg
body: And it looks like this feature "bug" isn't fixed (yet)!!


author: DJ Thornton
body: I just ran into this situation as well. With [@Nick Cruickshank](/t5/user/viewprofilepage/user-id/3117251)'s suggestion I was able to update the color/uptime for the affected day, but as [@Vishal.Shah](/t5/user/viewprofilepage/user-id/1356997) \& [@Jeremy Goldsmith](/t5/user/viewprofilepage/user-id/3841971) mention it's essentially orphaned from the backfilled outage.

I've opened a ticket with Atlassian regarding this.