As a user, I want to be prompted to authenticate before seeing a start work modal

[mbeacom]

Currently, if a user is not logged into Gitcoin and they click on Start Work, they are still prompted with the start work modal. Once they submit the modal, they receive the notification that they must authenticate with Github.

We need to alert them to authenticate and redirect them to the FTUX if necessary.

Estimated Hours / Rate

1 Hour
$20 USD / hr

Reviewers

@PixelantDesign @vs77bb @owocki @mbeacom @thelostone-mc

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 0.028 ETH (20.5 USD @ $732.02/ETH) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $8,005.52 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

1. @arun1595

has committed to working on this project to be completed 11 months, 4 weeks from now.

[bakaoh]

I think the 'start work' button should show 'login to start work' if user didn' t login

[thelostone-mc]

@arun1595 when you get to it -> could you update the alert to use our custom alert aka
_alert({message: '....'}, 'error');

[arku]

@thelostone-mc Sure!

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 0.028 ETH (20.95 USD @ $748.38/ETH) has been submitted by:

1. @arun1595

@mbeacom please take a look at the submitted work:

• PR by @arun1595

---

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
  $8,609.18 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

The funding of 0.028 ETH (20.47 USD @ $731.2/ETH) attached to this issue has been approved & issued to @arun1595.

• Learn more at on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $7,001.64 more funded OSS Work available on the Gitcoin Issue Explorer

[gopye]

This issue should be automatically removed from https://gitcoin.co/explorer. Also doesn't look like these are updating correctly.

[owocki]

@mbeacom

did you open up a second bounty for this issue?

there seems to be two, and the second one is showing up on gitcoin -- thats why the gitcoin funded issue is showing as 'open'

https://beta.bounties.network/bounty/v1/383
https://beta.bounties.network/bounty/v1/483

[mbeacom]

@owocki Not that I'm aware of. The linked bounties seem to be for kennethashley and cryptotracker bounties?

[owocki]

is your metamask on the mainnet? this is what i see when i view them on the mainnet http://bits.owocki.com/1I3s451e3n0i/Screen%20Shot%202018-05-24%20at%2011.26.15%20AM.png

[owocki]

maybe one of your tx's got rebroadcast?

[mbeacom]

Whoops! Yeah... - This must have been the transaction that popped back up in my metamask interface to confirm. Ew...

[thelostone-mc]

@weberV Looks like it's a script execution gone wrong ?
It's spammed all over the place.
Would you be kind enough to undo the changes and remove the comments across all our issues ?

Thanks in advance!

[gokulkrishh]

@mbeacom Is this issue still open?? I can see it was opened back in gitcoin but closed here

[gomesalexandre]

Issue still shows as opened on Gitcoin currently

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

The funding of 0.028 ETH (16.12 USD @ $575.67/ETH) attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $11,399.18 more funded OSS Work available on the Gitcoin Issue Explorer