Improve job events filtering

[jojedev]

We need to filter our events in order to get:

• Multiple applicants messages working
• Display all the neccesary job events that doesn't have a recipient address once a job has started and messages events.
• Make sure that those events doesn't get displayed if the job state comes back to OPEN and owner decides to change workers.
• Use index, so let's say a jop was assigned to pat. we'll get all the events from that event till pat is no longer being part of the job

\src\app\dashboard\jobs[id]\page.tsx On line 207.

little example:

I'll work on this later

[jojedev]

dade3f0

[jojedev]

@kasumi-1 Basically now we have the same functionality as before for a job that is open and has multiple applicants, but now if its taken it will find the last worker assign event and show you all the events from that point on, till it finds another job assign, if it does it will do the same.

[jojedev]

Pat suggested a collapsible to show all the previous events, but when I spoke with Tomas (some time ago) about that he told me that we wouldn't show all the past events. Would like your opinion on this

[jojedev]

I spoke this with Tomas and told me that for now isn't neccesary to work further on this and I think it makes sense, will close this

[kasumi-1]

so if a worker delivers a result to a client, then they start a new job, how does the client then see the past deliverables?

i think its impossible to make the history inaccessible without causing many similar problems. i prefer being able to look at my past history, esp with many recurring jobs with same workers.

[kasumi-1]

i think impl of #89 may do some of the heavy lifting here

[jojedev]

@kasumi-1 would you please provide more information about what is required here? I'm a bit confused