Web: as a user, i want gitcoin.co/inbox, so i can manage my notifications (and action items)

[owocki]

User Story

as a user, i want gitcoin.co/inbox (or gitcoin.co/notifications), so i can manage my notifications

Why Is this Needed

its easy to lose track of your notifications

Summary:

Description

Type: Feature

Current Behavior

No inbox

Expected Behavior

Inbox

Definition of Done

User can go to gitcoin.co/inbox and see a list of notifications.

• notifications can be selected or unselected. there will be 'select all' or 'deselect all' buttons on the top, and there will also be 'mark selected as read', 'delete selected' and 'mark selected all as unread' buttons'
• notifications will be sorted chronologically and paginated
• notifications can be marked as read, marked as unread, or deleted
• each notification has a 'go' button next to it which will allow the user to process the notification (whatever action is associated with it).. when a user clicks 'go' the notification will be marked as read.

This page will be linked in the top right nav, under my user profile.

Notifications will be generated each time a user needs to take action upon something (approve worker, disapprove worker, accept worker, receive tip, etc)

Suggested model for notifications

• pk
• created_on
• is_read (default = false)
• deleted (default = false)
• copy
• action url

[mbeacom]

@owocki We received feedback from Richard Burton during ETHIndia to implement something similar. Do you think it'd be worthwhile to include some visual queue in the nav under user to indicate new/unread notifications are available?

Also, it was conveyed that a central place to manage all of a user's gitcoin centric items would be ideal. Kind of like the dashboard, but ultimately, you'd always be dropped onto "Your area" if you're logged in, opposed to the standard gitcoin landing, similar to being logged into FB, etc. Any thoughts on this? @PixelantDesign @vs77bb
Am I missing anything from that conversion? @thelostone-mc @SaptakS

[PixelantDesign]

Thanks for putting this ticket together @owocki @mbeacom

A central place for notifications is a good idea. I think it makes sense to surface maybe top 5 recent actions on the dashboard and then direct users to the Inbox to see all and manage their notifications.

Dropping users on a dashboard (your area) also makes sense, vs. starting on the landing page which is more for marketing.

[owocki]

@owocki We received feedback from Richard Burton during ETHIndia to implement something similar. Do you think it'd be worthwhile to include some visual queue in the nav under user to indicate new/unread notifications are available?

yes

Also, it was conveyed that a central place to manage all of a user's gitcoin centric items would be ideal. Kind of like the dashboard, but ultimately, you'd always be dropped onto "Your area" if you're logged in, opposed to the standard gitcoin landing, similar to being logged into FB, etc. Any thoughts on this? @PixelantDesign @vs77bb

agree

A central place for notifications is a good idea. I think it makes sense to surface maybe top 5 recent actions on the dashboard and then direct users to the Inbox to see all and manage their notifications.

agree

Dropping users on a dashboard (your area) also makes sense, vs. starting on the landing page which is more for marketing.

agree.

should we bounty this @PixelantDesign @mbeacom or should we put it on the core contrib's radar for sept? assuming its a priority.. that is

[PixelantDesign]

This seems like a big feature, let's build this in-house, thoughts? @owocki @mbeacom Is there any ground work that we can lay while we figure out the ux of the front end? Curious for planning purposes.

[owocki]

yes having the frontend built already would be really useful

[willsputra]

will help out on this cc @PixelantDesign 🙂

@owocki are we going to have different types of notifications?
for example:
• issue-specific notifications would look different from, say, a general announcement
• different types of notifications would have different icons (like Facebook)

these would help users to visually differentiate the notifications more easily.

if we're going to have different types, I guess listing down the possible types would be a great first step!

[owocki]

@owocki are we going to have different types of notifications?
for example:
• issue-specific notifications would look different from, say, a general announcement
• different types of notifications would have different icons (like Facebook)

@PixelantDesign what do you think of this idea? my instinct is to keep it simple for v1

[vs77bb]

Agree with keeping it simple and having them all in one place for now, imho. Some notifications that come to mind:

For Funders

• You have workers to approve on this issue.
• Your bounty hunters hasn't responded on this issue in a few days. Remove them if you haven't heard from them?
• There is a submission against your bounty.

For Hunters

• You haven't responded to this issue in _x_ days
• This issue has been remarketed and has your skillsets. Are you interested?
• A funder seems to have left you a comment here

Anything else?

[willsputra]

Noted on keeping it simple for now.

A few more notifications:

For Funders
• Your bounty hunter has stopped work.
• Your bounty is expiring soon.

For Hunters
• You have been approved / disapproved for a bounty.
• You have been removed from a bounty due to no response.

[vs77bb]

@willsputra Agree with these. Happy to provide feedback once you get something going here!

[willsputra]

Here's a draft for notifications:

higher-res jpg:

thoughts? 🙂

[PixelantDesign]

Very exciting @willsputra!

If I've read a notification and acted upon it, my instinct is, it should not show in the list of 5 (in the drop down). Cleans it up so that only the newest show. Thoughts?

Adding the list of potential notifications we discussed:

For Funders

• You have workers to approve on this issue.
• Your bounty hunters haven't responded on this issue in a few days.
• Remove them if you haven't heard from them?
• There is a submission against your bounty.
• Your bounty hunter has stopped work
• Your bounty is expiring soonYour bounty has crowdfunding added to it.

For Hunters

• You haven't responded to this issue in x days.
• This issue has been remarketed and has your skill sets. Are you interested?
• You have been approved for a bounty
• You have been declined for a bounty
• You have been removed from a bounty due to no responseYou have received a tip.
• Your submission has been approved
• Your submission has been declined.
• Funding has increased on a bounty that you’re working on.

@owocki @mbeacom @thelostone-mc @vs77bb

[owocki]

this looks really good!

my only comment: lets me make sure it will collapse to be mobile and look good there too!

[willsputra]

@PixelantDesign makes sense! what happens if you have so many unread messages though? maybe we could put a scrollbar to prevent it from becoming too tall?

[willsputra]

@PixelantDesign @owocki draft for mobile. thoughts?

[PixelantDesign]

@mbeacom @thelostone-mc @SaptakS will one of you guys review and provide any tech guidance before we bounty this?

[owocki]

i feel like it's fairly straight forward.. it should just be a new app named 'inbox' with one model Notification that has the following fields

• pk
• created_on
• to_user_id
• from_user_id
• CTA_URL
• CTA_Text
• message_html
• is_read (bool)

we will likely also want an easy helper function that can be used to create new Notifications

[PixelantDesign]

@willsputra It looks good...please upload sketch file!

I'll create a new clean ticket.

[PixelantDesign]

Closing this one and moving to a clean ticket #2404

[vs77bb]

👍