How does it behave when #669 (closed) is checked at "no"?
Do we agree that the badge on the menu is the number of job offers I got notified for and not the number of new job offers since the last time I visited?
How do I mark the badge as read? By reaching each notification one-by-one? By reaching all notifications?
How does it behave when #669 (closed) is checked at "no"?
That's a good question. I think we should have on switch for chat notifications, and another one for job board notifications. Easily doable?
Do we agree that the badge on the menu is the number of job offers I got notified for and not the number of new job offers since the last time I visited?
Yes. Would we easily be able to know that some job offer was posted since the last time I visited the job board?
How do I mark the badge as read? By reaching each notification one-by-one? By reaching all notifications?
I'm not sure I understand the question but in my mind the behavior is that same as the notification drawer. If you visit a job offer's detail page, than you get one notification less on the badge. Makes sense?
I think we should have on switch for chat notifications, and another one for job board notifications. Easily doable?
So if I check it on "My Profile" it will only involve mention and message notification type and if I check it on My Main Skills it will involve joboffers's type. @sophie Is it OK to have both on different places?
Would we easily be able to know that some job offer was posted since the last time I visited the job board?
Doable at least, technically:
Add a field to the user, storing an array of seen job offers urlids.
From the job offer component, retrieve this array, invalidate missing entries (old ones, depreciated/removed), save the new array to optimize next load.
On badge, or somewhere else, show the delta between this array and the number of job offers.
Whenever the user see a job offer, update this array & save it.
If you visit a job offer's detail page, than you get one notification less on the badge. Makes sense?
Sure. I just feel that this behavior is a bit clumsy:
I have 3 notifications for new job offers
I click on "Job offers" on the menu, I see the job offers page, maybe I see ones from my notifications - maybe not, depending on the volume of job offers sent & on my skills.
I still have a "3" on my menu, until I click on the bell and click on each one of those notifications or that I find them on the job board and click on the offer's title
Sure. I just feel that this behavior is a bit clumsy:
I kind of agree, but then... that's a feature. If you are not interested in notifications... deactivate them :-) The positive side that I see in this is that people with notifications on will actively look at job offers that match their skills, and update their list of skills if they don't want to be bugged with things they don't actively sell.
@sophie worth having your opinion I believe even though I think I'd prefer to give it a try first and see, but your opinion matters as always
Yes, for sure, which one? I feel that "Edit my profile" is the place, but maybe not? @sophie
What does "see a job offer" mean?*
I'll watch the populate event from the job board component, this way whenever a resource is populate => this resource is shown to the user, regardless of if it's on the all job offers or on an individual job offer view.
If you are not interested in notifications... deactivate them
I'll watch the populate event from the job board component, this way whenever a resource is populate => this resource is shown to the user, regardless of if it's on the all job offers or on an individual job offer view.
Sounds like something that would work then. If we can signal on the menu entry that some new offers were posted since the last time you visited, even though they do not match your skills, that's awesome. See with @sophie how.
So if I check it on "My Profile" it will only involve mention and message notification type and if I check it on My Main Skills it will involve job offers's type. @sophie Is it OK to have both on different places? <
I think it's worth having a try on "mark offer as read after user goes on offer page".
But if we don't want it to be a nightmare for user he needs to be able to receive notifications only for the skills he picked. Receiving notifications for all job offers is non sense
receive notifications only for the skills he picked
That's the subject here, no worry.
The question is : Should the badge on the menu display the number of unread notification related to job offers with your skills you have or the number of new job offers since last time you visited?
gather all notifications settings
To be sure, settings are:
Receive an email when receiving a notification about mention/message on chat
Receive an email when receiving a notification about a job offers
Receive a notification about communities I subscribed to
Checking the third without the second will leave me a notification every time there are a new job offer related to my main skills on a community I subscribed to but it will not send me an email.
About the where, as all of this is a pretty big change, I'd like to make/release it this way:
From Edit My Profile, I can check "receive email for all notification"
Implement Community subscriptions with notification per communities
Move "receive email for all notification" to this page
Split "receive an email for all notification" to "receive an email for mention/messages on chat" and "receive an email for job offers things"
Improve the notification per communities to handle related to main skills part
@sophie Should we keep the "I want to receive email [...]" on the view "My Profile" (not edition) or remove it on step 3?
Should the badge on the menu display the number of unread notification related to job offers with your skills you have or the number of new job offers since last time you visited?<
Badge should show the number of notifications with your skills, for which you haven't visited the page offer yet.
Receive a notification about communities I subscribed to<
is not very precise to user, what does it mean ? Which kind of info will I receive in my notifications ?
Your steps sound good to me.
We can remove "I want to receive email [...]" on profile page and put everything in the setting page. Maybe add a bloc on the main dashboard to inform about the existence of this new page.
@jbpasquier
yes text is for both the e-mail and the notification drawer :
Author in Offre de mission : title of job offer
Exemple :
Maurice Dupont dans Offres de mission : Cherche développeur PHP Paris à plein temps
Maurice Dupont in New projects : Full time PHP developer in Paris
Move "receive email for all notification" to this page: 6 tokens
Split "receive an email for all notification" to "receive an email for mention/messages on chat" and "receive an email for job offers things": 18 tokens
Improve the notification per communities to handle related to main skills part: 120 tokens
@alex Although it might be interesting, this is not the feature HDP is asking for. We want first a conversation thread along with the mission and a basic manageable status of the mission (opened, closed).
When we discussed it, notifications were included in the need. Are you saying you guys are totally fine without notifications on the job board? How will you know when someone let a message?
@alexbourlier Yes I'm sure. I'm not saying we don't want that (actually I just said the contrary). I say it's not our priority. The two priorities defined by HDP are:
Discussion thread along with the mission
Invoice component as it was designed by Sophie
We can discuss going further with notifications but we are waiting to know how much those 2 features will cost before biding on others.
@alexbourlier Not sure what to do with that. Are we saying that we don't want notification for job offers and that we don't want to see only subscribed communities on the job board?
Do we have a feature request describing the need for those?
I'm also wondering: If no one is willing to fund this one for now or for the next month - time validity of this estimation, how should we handle this? It can become a dead feature polluting the mockup. (@rachel for notice)
@jbpasquier The notifications are not on the priority list for HDP. They want to know first what would be the cost for their top 2 priorities.
I'm creating a feature request right now. Sorry about the delay, I'm new at using Gitlab and try to figure out where to post my request :)