Component sub-groups
Asked by Ed Crawford:

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.


Answers:
author: Mubeen Mohammed
body: Hello [@Ed Crawford](/t5/user/viewprofilepage/user-id/70875)

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.](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html)

I hope the information provided is helpful.

Regards

Mohammed Mubeen

Cloud Support Engineer

comments: author: James Tompkins
body: 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.


author: Johann B
body: 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>


author: Egor
body: 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


author: Maksim Nesterenko
body: 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?


author: Abraham Musalem
body: Hi Maksim,  

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.   

Best,  
Abraham  
Statuspage Support


author: Darren.Burrows
body: 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.


author: Muhammad Zeeshan
body: Hey [@Darren.Burrows](/t5/user/viewprofilepage/user-id/5260381)

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.


author: Rathish.Gopalakrishnan
body: Hi Atlassian team,  
Do you have any update on the ETA for this request as we are heavily relying on the 'multi-level grouping of components' feature to be introduced in our project?

Thanks,


author: Russell Chee
body: Hey [@Rathish.Gopalakrishnan](/t5/user/viewprofilepage/user-id/2446870),

I hope you are well and thank you for your interest in this feature request.

I would like to set expectations that we cannot guarantee an ETA on a feature request being implemented this is determined by our product team alongside our development team.

Having said that what I can do is add your voice to the conversation and share your use case as part of the internal comments on the feature request itself.

I can understand how a functionality like this would be useful for you and your team so please keep an eye on this community post for updates or reach out to us in a support ticket to find out any updates. Have a great one!

Russell


author: Turgeon_ Benoit
body: +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.


author: Keval Parekh
body: 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


author: dmitry.korolev
body: +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.


author: Massimo Gelli
body: Hy,

We also need to have a group hierarchy and are interested in the possible release date

comments: author: Mubeen Mohammed
body: Hello [@Massimo Gelli](/t5/user/viewprofilepage/user-id/4483153)   
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.](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html)

I have added this request internally to the Feature request for the engineering teams' visibility.

I hope the information provided is helpful.

Regards

Mubeen Mohammed

Cloud Support Engineer


author: Clint Payton
body: +1 for University of Idaho and our desire for nesting / sub groups. Seems like an easy win.


author: Chris Hoiland
body: +1

sub components will be a deciding factor on which status page solution we go with to replace our legacy system.


author: Kyle Hardin
body: 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.


author: luisfrancisco.hernandezreyes
body: +1  
hi everyone  
I 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


Tags: cloud