Email component subscriptions through API showing blank values

[Balamurugan Pasumpon]

Our organization using audience specific statuspage. When adding new components and associated with the group, these components are not automatically subscribed to email notifications. We have to manually subscribe the components from management pages which is a tedious task to enroll for multiple users. So we have decided to update the component subscription through API and we done it successfully. However, when we export the users from audience page for validating, the 'Email component subscriptions' column of csv file displays blank values. This only occurs when updates are made via the API. Is this an existing issue? Can you assist in resolving this issue?

[Darren_Burrows]

We also use audience specific pages and I believe this is expected behaviour. 

If you're signing them up to all components the subscription set will return as blank on the CSV, this is because statuspage records both if you are a subscriber and what you are subscribed to. So if the list of subscriptions is blank, statuspage assumes that user is subscribed to all components. 

You can prove this by using API to sign up users to components, if you send a request that contains no components, statuspage will sign that account up to all components. 

[Balamurugan Pasumpon]

Thank you @Darren_Burrows 

I am fine with this being anticipated behavior, but when I manually update subscriptions from the admin pages, I receive the values correctly in the csv.

[Darren_Burrows]

Is that for when a sub has all options or just some, because I have yet to see this being the case regardless of how we update a subscriber where they have all options selected. I only ever see specific components listed when they have one or more selected, but not all. 

[Balamurugan Pasumpon]

Atlassian team opened a bug ticket to the development team for empty components in Export to csv file when calling the update subscriber endpoint.