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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,458,594
Community Members
 
Community Events
176
Community Groups

Link to external / third-party StatusPage

This is probably more of a feature request but I'll try my luck.  I think it would be useful if a link was available to the third-party Statuspage for any added to your page.  This would provide better context of a component status such as any description etc.  Is there any way to do this currently?

1 answer

1 vote
Zach Atlassian Team Apr 13, 2021

Hey Chris, 

While there isn't any default functionality it could be possible through the use of HTML/JS to embed an HREF in the component name. 

Another option is that we have some markdown support that you could use to make the component named something like 

<a href="https://www.google.com">Brand New Api Service</a>

Which would then let you select the component name to get taken to a given pages url. 

Hopefully this helps! 

Thanks @chris.johnston for the question ans @Zach for the answer!

 

I bumped into this one as well - and looks like the markdown support could be the ok answer here as I guess that's the best way to let people to "connect" to the details of the 3rd party incident (as, the 3rd party incidents do not inherit from "upstream").

 

I would suggest adding this to the docs also - meaning, letting people know when they add components (if it really is not there yet) - as this is quite necessary...

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events