standard bounties: multiple bounties per issue URL

[owocki]

how do we want to handle multiple bounties per github issue URL?

right now, via the current stdbounties UI... someone can submit mulitiple bounties on the same GH URL. this is confusing because while standardbounties supports it.. the gitcoin UI does not..

maybe we add a validation step if someone tries to enter a currently active bounty into funding/new, we tell them they can't (or solicit them adding funds to the bounty instead?)..

[jasonrhaas]

Right now once an issue is in the fulfilled state in Gitcoin, it doesn't allow people to add another fulfillment via the bounty details page. I believe this can be manually overridden by going to the /fulfill page directly.

Currently it adds the latest bounty to the stack on the Blockchain, and the "Acceptance" part just takes the latest one. It's non ideal but I was trying to go for somewhat parity features at first.

We can display in the UI somewhere that the bounty has been fulfilled by "John Smith" or whatever. I think with the Oauth stuff that was added we can pull the Github Email Address.

I think the best solution is to just display the multiple bounties that have been submitted right in the webpage. This requires an update to the database schema though, so this would require a migration so we have to be careful about how we do it.

[owocki]

i wasn't talking about multiple fulfillments per bounty... i was talking about multiple bounties per github issue.

might be easier to just chat about this on the phone?

[jasonrhaas]

Ah yes, I read that wrong. Correct, should be a check in there to kick back if the github issue already exists. That should be an easy fix.

[jasonrhaas]

Ok so now before kicking off the process it checks that database to see if that issue is already in there. If it is, it pops up a banner. We can probably do more in the future but I believe this is feature parity for the moment.

[jasonrhaas]

a2cf8c5