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
Community Members
Community Events
Community Groups

How to indicate affected components when backfilling an incident

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? 

1 answer

1 accepted

0 votes
Answer accepted



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.



Top moves, Nick; thank you very much!

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

Like Jeremy Goldsmith likes this

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.

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. 

Like # people like this

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? 

Like # people like this

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. 

Like John Hellenberg likes this

And it looks like this feature "bug" isn't fixed (yet)!!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Statuspage

New feature: Slack notifications for Statuspage

We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...

3,046 views 8 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you