Web: Gitcoin Issue Details: Activity Tune-Ups

[vs77bb]

What Is The Problem
Gitcoin's Activity Feed has a few bugs which could be worked out to make the experience cleaner for people who are looking to grok the history of a bounty.

_Severity:_ P2 / P3 Bug

How can this be fixed?

• [ ] Remove comma (",") in the 'Work Started' section, as it's only one name.
• [ ] For Auto-Approvals, add an 'Activity' stating someone was auto-approved.
• [ ] For Auto-Approvals, ensure Gitcoin Bot comment updates on Github to state the auto-approval (see 2nd screenshot below where this didn't happen).
• [ ] For all approvals, explicitly state who is approved ([Minimal] design needed? @PixelantDesign @willsputra).

[willsputra]

For all approvals, explicitly state who is approved ([Minimal] design needed? @PixelantDesign @willsputra).

My $0.02:

Existing layout

vs77bb is the funder who approved the worker, correct? However, at first glance I thought vs77bb is the approved worker. I guess for me the 'Worker Approved' card isn't so clear.

Suggested layout

Suggestion: provide more detail on the 'Worker Applied' card. This solves 3 things:
• It is clear which worker is approved (Anish-Agnihotri), and which is rejected (lordvader, being also grayed out).
• It is clear who approved who.
• Eliminates the need for the 'Worker Approved' card.

thoughts? @PixelantDesign

[vs77bb]

This is much better @willsputra, I like it! Thoughts below:

• "Approved by @vs77bb on Sept 9" could be one line, instead of two.
• In the auto-approved case, it can just say "Auto-approved on Sept 9"
• Also like the graying out of applied workers who are rejected.

Thoughts @PixelantDesign? Think we're good to bounty this from here?

[PixelantDesign]

The activity is based on time... oldest at the bottom—> newest at the top. I recommend adding Who was approved to Vs77bb block (otherwise we are adding new activity to old activity items).

[willsputra]

I see. In that case it would look like this:

• Would 'Approved Worker' be clearer than 'Worker Approved'? It's less confusing visually to me, since all the workers' actions start with 'Work' (Worker Applied, Work Started, Work Stopped...)
• Would it still be possible to gray out the rejected workers?

[PixelantDesign]

Looks great @willsputra! Worker Approved I think.

It's probably ok to show rejected workers.

We do need an email for rejected workers...something like this....
"Sorry you have been declined to work on this issue, but here are some other open issues"
See Issue Explorer Button.

cc:
@vs77bb

[willsputra]

Worker Approved then.

Sketch file here: https://drive.google.com/open?id=1p5xO52ZbE44wjZD7VOkW2Ibh-B1Uo16B

@PixelantDesign should I design the rejected workers email as well?

[PixelantDesign]

@willsputra Sure! That would be awesome!
Email template should be on the creative repo!

[PixelantDesign]

@vs77bb let's make a new ticket for the Build Bounty?

[willsputra]

@PixelantDesign draft for declined workers

[PixelantDesign]

@willsputra is there a way to make the email more whimsical? Like an apologetic decline?

The goal is to let users know that they've been declined but also show empathy and suggest a few issues that might be similar or related to their skillset. How can we let contributors down easy and still be encouraging at the same time?

[vs77bb]

@PixelantDesign Did you make a build ticket here or should I for the Activity Feed Tune Up?

I think the Declined E-Mail will be another ticket, but will make a comment here as well since we're discussing. Workers are declined some, but are more often simply ignored.

For example, in the above screenshot, Github User 'ysjwd' was not declined, but was 'passively rejected' because the funder chose someone else to work the ticket. I think that e-mail might require slightly different copy, maybe like:

It looks like the funder went with another applicant for this ticket. You weren't declined outright, so be on the lookout for potentially being selected down the road. Furthermore, we hope there's other work for you on the Issue Explorer! 

If not, feel free to make a [Gitcoin Request](https://gitcoin.co/requests/) for another open source project you'd like to contribute towards.

@PixelantDesign Does this copy let folks down easier?

[willsputra]

@vs77bb I like the idea! Modified it a bit here:

[PixelantDesign]

Looks great! I'll create a build ticket.

[kuhnchris]

I think this is done - closing.