Web: New bounty description pulls GH description and disregards the submitted description

Created on 30 May 2018 · 19Comments · Source: gitcoinco/web

User Story

As a user, I want to be able to add additional information in the description field for new bounties

Why Is this Needed?

Summary: Bounty funders should be able to add/remove/modify any bounty description before submitting the funding form.

Description

Type: Bug

Current Behavior

The bounty description reflects the github issue description, regardless of changes made to the bounty description post GH data pull.

Expected Behavior

The user should enter a github issue URL and the description pre-fills with the GH issue description.
The funder should be able to modify this pulled in description and be confident their changes to the description are reflected on the bounty details page.

Reproduction

Open the new funding form: https://gitcoin.co/funding/new
Enter a github issue url.
Wait for it to populate the GH issue data in the description field.
Update the description field to anything else.
Submit the form and wait for the bounty to post.
Check the description field on the bounty details page.

Solution

Summary: Update the form and following logic to no longer overwrite the submitted bounty description with the GH issue description, but continue to pre-populate the fields on the initial GH issue url entry.

Definition of Done

Funder form pre-populates with data from the GH issue, but respects the funders submitted values.

Additional Information

Feel free to reach out to a team member on Slack if you have any questions!

bounties bug community member frontend help wanted will tip for turnaround

Source

mbeacom

Most helpful comment

@gitcoinbot On it.

arku on 5 Jun 2018

👍2 😕1 🎉1

All 19 comments

@mbeacom I'll take a stab at this one.

arku on 30 May 2018

👍2

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

__This issue now has a funding of 0.03 ETH (16.99 USD @ $566.35/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
$10,573.76 more funded OSS Work available on the Gitcoin Issue Explorer

gitcoinbot on 1 Jun 2018

@arun1595 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] warning (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot on 5 Jun 2018

@gitcoinbot On it.

arku on 5 Jun 2018

👍2 😕1 🎉1

[x] warning (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot on 11 Jun 2018

@mbeacom I hate to release this but I couldn't figure out the issue :disappointed:

Stopping work on Gitcoin so someone else can fix it.

arku on 14 Jun 2018

Issue Status: 1. Open 2. Cancelled

__Work has been started__.

These users each claimed they can complete the work by 9 months ago.
Please review their action plans below:

1) ninjasun has started work.

I think this issue is not simple as it seems.Will try first to have a look around, then we will see.

Learn more on the Gitcoin Issue Details page.

gitcoinbot on 15 Jun 2018

@mbeacom An user story usually starts with the specification of the actor. Example: As a bounty founder, I want to be able to add additional information .. general word user is not so useful

ninjasun on 15 Jun 2018

@mbeacom mm it seems to test this form I need to submit it and post a bounty (as is written above). There must be a simple way to do it.

ninjasun on 15 Jun 2018

@ninja you can test it out on the rinkerby network (if that's what you were asking )

[ Open metamask -> change network from Main to Rinkerby and post a bounty on the local instance]

thelostone-mc on 15 Jun 2018

@ninjasun Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

[x] warning (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot on 18 Jun 2018

@thelostone-mc is there any documentantion regarding the networks available?
I'm still on it, having problem running the platform.

ninjasun on 18 Jun 2018

[x] warning (3 days)
[ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot on 24 Jun 2018

@ninjasun Ah sorry I was travelling and didn't see this

I don't think we've got docs on using it but it just a matter switching the current network on metamask

Boot up your local -> navigate to fund issue -> ensure metamask network == rinkeby -> Proceed to fund your issue with dummy ether. You can get the dummy ether from https://faucet.rinkeby.io/

thelostone-mc on 25 Jun 2018

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

@ninjasun due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

[x] warning (3 days)
[x] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

gitcoinbot on 27 Jun 2018

Hey @thelostone-mc, looks like this issue got buried, what are our next steps here?

ceresstation on 21 Nov 2018

Hey @ninjasun are you still working on it, or do you need some help from our side?

usmanmuhd on 24 Dec 2018

@usmanmuhd / @ceresstation Ah the behaviour we ended up going with was to not allow funder to add more data on the gitcoin ticket -> we sync with github to get the latest description
The periodic sync ensures we are always in sync with the data in github.

Aka github issue description serves as the source of truth

thelostone-mc on 6 Jan 2019

Issue Status: 1. Open 2. Cancelled

__The funding of 0.03 ETH (3.84 USD @ $127.88/ETH) attached to this issue has been cancelled by the bounty submitter__