You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
For our platform it would be really good to be able to have multi-level grouping of components rather than just one level. I know other status page services offer this. Will Atlassian be developing statuspage further to add something like this (or anything new?!?!). We use statuspage because it was an obvious choice for an organisation who is already using a number of Atlassian products BUT it seems pretty basic in terms of features/configuration.
Hello @Ed Crawford
Thank you for contacting the Atlassian community! this is Mubeen.
The ability to create subgroups under the component group option is currently not possible with the Statuspage product design. However, we have an open feature request with our engineering team. STATUS-43 is the ticket ID for your reference.
You can also read about our feature implementation policy.
I hope the information provided is helpful.
Cloud Support Engineer
Seems they aren't able to provide a link or even a location to add a feature request as these are only tracked internally by Atlassian. See https://community.atlassian.com/t5/Statuspage-questions/suggesting-a-feature-for-Statuspage/qaq-p/1527105
Hey James, Johann,
That is correct, we track all of our Statuspage tickets internally at the moment. We share the ticket reference in case you want to get updates for this specific ticket from our support team.
The full link would be https://jira.atlassian.com/browse/STATUS-43
so what's the status of the STATUS-43 ? Subgoups would be very useful to have a hierarchy of services like
* product name (group)
** region (subgroup)
*** specific service (component)
Are there any timelines on when it'll be available?
This is still under consideration by my product team as it's not a very popular request. However, this could always change. Feel free to check in in a few months to see if the status has been updated.
Is their anyway to float requests like this further up your priority list? You mentioned that its not a very popular request, is this based on customer feedback or internal views?
I think have StatusPage feature requests visible would be beneficial for everyone, since it would allow the wider user group to vote on things like this - I know in terms of sub groups, we worked around it, since we decided it was easier to do this than to put in a request and wait, which makes me wonder how many other feature requests have been overlooked by users because they have work arounds in place.
The priority of a feature suggestion is based on multiple factors. Since Statuspage feature requests are private we collect the data on how many customers asked for that functionality and add it to the internal ticket. In addition to that, we take insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
As for making the Statuspage feature requests public, I shall forward your feedback to the appropriate team and this is something already being actively considered. In the meantime, we are making sure to convey the status of the feature requests with our customers as readily as possible whenever they reach out via any of our Support channels and mention any workarounds where possible to ensure that the requirements are fulfilled to the best of our abilities.
Hope this sufficiently answers your query and please feel free let us know if you need any further assistance.