Issues with component subscription

[Pierre Bosisio]

Hi,

I'm trying to figure out how to make the settings right so that users only get nofitications when a specific component in an incident gets changed...It doesn't seem to work...

I was informed that the components subscription feature is full of bugs... is this true ? can this explain why I can't get this functionnality to work as expected ?

Thanks,

[Egor]

Hey Pierre, 
Thanks for reaching out to Atlassian Community!

The component subscription feature in Statuspage is designed to let users subscribe to specific components and receive notifications when incidents affect those components. However, there can be certain limitations or issues based on the specific configuration or usage.

If you’re finding that users aren’t receiving notifications as expected for component-specific incidents, here are a few considerations:

1. Check Subscription Settings: Ensure that the subscription preferences are correctly set up on both the user and admin sides. Users should be able to subscribe to specific components, and notifications should be sent only when those components are affected.
2. Notification Settings: Verify that the incident notification settings are configured to include all relevant stages (e.g., updates, resolved notifications).
3. Known Issues: While there may be occasional bugs reported with component subscriptions, they are not universally problematic. It’s possible that specific edge cases or configurations may lead to unexpected behavior.
4. User Email Filters: Sometimes, users might not receive notifications due to email filtering or spam rules on their end.

Best Regards,
Egor