Skip to content
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

[NV-1606] 🚀 Feature: Notification groups #2640

Open
2 tasks done
altsst opened this issue Jan 29, 2023 · 8 comments
Open
2 tasks done

[NV-1606] 🚀 Feature: Notification groups #2640

altsst opened this issue Jan 29, 2023 · 8 comments
Labels
enhancement New feature or request linear triage

Comments

@altsst
Copy link

altsst commented Jan 29, 2023

🔖 Feature description

The ability to group notifications to a specific item (e.g: a task, a project)

Where multiple notifications to the same task are being grouped together (just like in jira and clickup):

image

🎤 Why is this feature needed ?

for complex applications where a lot of notifications are appearing grouping them into groups to outline the different sections would really be helpful

✌️ How do you aim to achieve this?

I want the headless react hook to return notification groups.

Where someone

  1. changes the name of a task X
  2. notification to group X is being added and the entire group will be shown as the first notification group

🔄️ Additional Information

No response

👀 Have you spent some time to check if this feature request has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

None

NV-1606

@LetItRock LetItRock changed the title 🚀 Feature: Notification groups [NV-1606] 🚀 Feature: Notification groups Jan 29, 2023
@jainpawan21 jainpawan21 added the enhancement New feature or request label Jan 29, 2023
@oba2311
Copy link
Contributor

oba2311 commented Feb 15, 2023

Thanks @altsst !

Could you please share mode details - do you refer to the notification center specifically? We do have feeds over there, which are not the same but similar.

Thanks

@altsst
Copy link
Author

altsst commented Feb 16, 2023

Of course @oba2311,

I am mainly talking about the headless useNotifications hook.

Let's take a todos app for example:
Notifications should look like this: (pseudo)

[
  { groupId: 'task_1', notifications: [ {..name changed..}, {..assignee changed..}, {..new comment..} ] },
  { groupId: 'task_2', notifications: [ {..status updated..} ] },
  { groupId: 'task_3', notifications: [ {..new comment..} ] },
]

I haven't found anything like that in the novu.co documentation.

@oba2311
Copy link
Contributor

oba2311 commented Feb 20, 2023

To me this sounds like what you have in mind is actually Topics.

@oba2311
Copy link
Contributor

oba2311 commented Feb 26, 2023

Putting this on hold unless we hear back from opener.

@altsst
Copy link
Author

altsst commented Mar 14, 2023

@oba2311 Topics seem to be only for sending notifications to multiple users.

And not for getting the desired notifications data structure (#2640 (comment))

@oba2311
Copy link
Contributor

oba2311 commented Mar 22, 2023

@scopsy - could you take a quick look here? I might be missing something. thanks

@scopsy
Copy link
Contributor

scopsy commented Apr 2, 2023

@altsst have a point here @oba2311, those are unrelated things as topics is about sending notifications an fanning them out. We don't have any functionality as of today to fetch notification based on those groups.

@altsst to better understand your usecase, you are using topics to trigger to those entities for example the group: "This is something" is a topic?

If that's the case, we would need to a allow optionally group the feed by "topicKey" in that case, as we don't have something like this today.

@altsst
Copy link
Author

altsst commented Apr 6, 2023

@scopsy Correct! And the items beneath it are the associated notifications/updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request linear triage
Projects
None yet
Development

No branches or pull requests

4 participants