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.
Regards
Mohammed Mubeen
Cloud Support Engineer
We would also like to see mulltiple levels of components, or sub components. I would like to add our use case and comments to the featuree request. How do I find STATUS-43? Hint: a link would be nice.
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 Thanks,
Egor
Hy,
We also need to have a group hierarchy and are interested in the possible release date
Hello @Massimo Gelli Thank you for contacting the Atlassian Community!
Unfortunately, we can't guarantee an ETA as our product team will make a decision together with our development team. The Product team reviews all feature requests and prioritizes those with higher demand to be implemented first. Any FR will take a varied amount of time until is ready if considered since it needs to go through Design, Development, Testing, and rolling out to production. You can follow the URL to further understand the feature implementation policy.
I have added this request internally to the Feature request for the engineering teams' visibility.
Mubeen Mohammed
+1 for this feature request.
In our organization we would like to have another level of nesting for internal status pages to display additional level of granularity, which is very useful for internal communications.
Hi Atlassian Team,
We would greatly appreciate it if you could expedite the addition of the multi-level grouping feature for components on status page. This enhancement would significantly improve our ability to organise and present information effectively. Thank you for considering our request.
Best regards,Keval
+1hi everyoneI add my comment: we need to have a sub group because we have several groups with several components for many sub services and regions one more vote for subgroups initiative
I would love to add my support for feature request STATUS-43 as well. Sub-components were the first thing my org looked for during our Statuspage trial, and ended up being a deciding factor for us versus other solutions.
+1x1000. Perhaps that will move the needed in your product management team lol ?It's such an obvious feature that's missing from an already excellent product. Nested groups shouldn't be that difficult to implement... say 1 sprint ? It's also a UI issue: once you have dozens of services, nested groups are invaluable to give a proper view of service health to a broad range of audiences.
+1
sub components will be a deciding factor on which status page solution we go with to replace our legacy system.
+1 for University of Idaho and our desire for nesting / sub groups. Seems like an easy win.
+1, could you please share with us STATUS-43 issue for tracking purposes?
+1 for this feature request. Existing user of Status Page. It would make it much easier to organise our services if we could use multi-level component groups. It appears there is a lot of interest for this feature, but not a lot of interest from Atlassian team in implementing, which is a shame.
Hi I am also looking for this feature to be implemented. Seems like there are a lot of other customers waiting for this feature as well. Is it possible to be prioritized based on the high need?
Also interested in this feature
Same here! This would be so useful!
+1; we would view this as a significant improvement, coming from an organization where product lines, individual products, and systems within each product would be better accomodated by a group/sub-group hierarchy.
It looks like you're new here. Sign in or register to get started.
