-
Notifications
You must be signed in to change notification settings - Fork 212
Broadcast Notifications Backend #4033
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Please verify in the dev backend. Test 1- let's do the following broadcast message: "Topcoder Bug Hunt now live. Join the hunt today!" Additional recipient groups may include:
|
@lakshmiathreya , can you please help me test this functionality? |
{ |
Please note - on DEV "QA" skill is not available. So for testing purpose I am pushing same message for "Node.js" skill to test it. |
@luizrrodrigues , Will we be able to see this notification in the notifications popup on the front end? @sachin-maheshwari @lakshmiathreya , How can we test if this notification is available to the target users? |
@SathyaJayabal not sure if that will be able on community front-end pop-up or not. You can find it in backend api response by using your JWT "user-token". For example - https://api.topcoder-dev.com/v5/notifications/list?read=false or https://api.topcoder-dev.com/v5/notifications/list?read=false&platform=community&per_page=2 I think, need to incorporate the broadcast message structure in front-end. |
Just further explaining the broadcast message design - @Oanh-and-only-Oanh As per my interpretation on this - you want to send this message to all public QA member. correct ? For sending message to private/specific group, we need to mention in "groups" field as "," separated like - same message can be send for community member who is part of any group 'A' , 'B' or 'C' |
@sachin-maheshwari, correct to your question above. |
@Oanh-and-only-Oanh I just want to confirm the definition of "public" member in our Topcoder system. As per me, public member will not belong any "private group". correct ? |
Verified the various tracks, groups and skills filter in dev backend. |
No description provided.
The text was updated successfully, but these errors were encountered: