Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Pinning Statuspage uptime graphs to the TOP of the Status Page

Does anyone have any example code of how to pin, or keep, the uptimes graphs at the TOP of the status page. Incoming incidents are pushing the graphs FAR down the page. I would rather have the graph stay at the top.

I might even like disable the showing of the incidents if that is possible and JUST have the graphs. 

I am not a programmer. Your help is appreciated. 

2 answers

0 votes
John M
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 09, 2022

Hi @Randy Everett ,

We have some JS snippets that can help with that.

Inserting this code into the Custom HTML Footer will move the components above the incidents: 

<script> $('.components-section').insertBefore('.unresolved- incidents'); </script>

You can remove incidents completely with this one: 

<script> $('.unresolved-incidents').remove(); </script>

You only need to add the opening and closing script tags once if you have multiple code snippets.

Also, be sure the syntax highlighting is working. Here is a video of pasting code into the editor, where the syntax highlighting is initially broken ('incidents' should also be red) due to the line break, but is easily fixed by backspacing once at the beginning of 'incidents'

2022-09-08_16-53-39 (1).gif

I'm wondering if there have been any updates to this?  Nothing happens when I use the snippet to move components before the unresolved incidents:  

<script> $('.components-section').insertBefore('.unresolved- incidents'); </script>

However removing incidents completely works fine with this one you mentioned above:  

<script> $('.unresolved-incidents').remove(); </script>

John M
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 12, 2023

Hi @John W ,

The code should still work. Is the syntax highlighting working? If not, the screen video above shows how to fix that. 

Yes the syntax highlighting looks to be working fine, but for some reason it's not working (all the active incidents are still showing at the top).  Weird, but like I said if I use the code to remove the active incidents it works fine.   

Looks like I finally got it to take just by playing around with the text and re-typing it manually.  Thanks!  

Like John M likes this
0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 09, 2022

Hey Randy,

Thanks for reaching out to community. Abe here with Statuspage support. You should be able to achieve this by using something similar to this code snippet which moves the components section above the incidents section. YOu will need to put this in the footer: 

<script> $('.components-section').insertBefore('.unresolved- incidents'); </script>

 You can find more basic code snippets here:

-Abe, Statuspage Support

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events