Show incidents of last 3 months

Question

Hi Team,

I have couple of queries, Looking for quick help.

1. By default the status page displays the incidents of last 15 days. Can we configure it to list down the incidents of last 3 months?

2. The incident timestamp is being displayed without year. Can we show the year as well?

Thanks in advance!..

Kevin Patterson_u4sm4w · Answer

I see, I usually work with clients that want to Trim the days, not increase so I defaulted to this page out of habit. Thank you for correcting me Karthik.

I'm sure you have seen it but the link at the bottom of the page "incident history" will redirect to the /history page in statuspage shows that will show all incidents. What I have seen most clients do is minimize the days on the main page (usually 7 days or less) and keep the link at the bottom that redirects to the history page. That said if you are wanting more to be shown on the main page it might be possible with the combination of an embedded javascript and html/css override to properly display the data.

The approach I would try would be to embed a javascript in the HTML footer that retrieves the incidents from the history page (/history) over the last 90 days. Then edit the HTML override section to display the results in an unordered list (ul). you will probably have to filter to account for the days that are already there by default.

Karthik Balakrishnan_xd3437 · Answer

Thanks Kevin,

But thats not helped. The script/css is used to reduce the number of days.

The expectation is to fetch more days of incidents.

Kevin Patterson_u4sm4w · Answer

Hi @Karthik Balakrishnan ,

While this is not something you can do in the GUI, this can be done with HTML/CSS overrides available in Statuspage for your first use case. Atlassian published a document with common use cases scroll down to "Show fewer days of history on the main status page" section.

https://support.atlassian.com/statuspage/docs/css-and-javascript-snippets-for-customizations/

I suspect it is also possible to provide the year via an override to solve your second use case as well, but it is not something I have had the need to solve for yet myself.

KP