Web: UX Add Project Type + Approval Settings to Issue Details

[vs77bb]

User Story

As a funder, I'd like the ability to toggle easily between 'Approval Only' / 'Permissionless' bounties and 'Contest' / 'Cooperative' / 'Traditional' bounties so that I am less prone to unrecoverable user error.

Why Is this Needed

Summary: Without this feature, I don't have a good way to make changes to the bounty details if I want to make it approval only / cooperative / etc. once I post the issue. I can only cancel and re-do, which isn't elegant.

Description

Type: Feature

Solution

Summary: Simple solution would be an 'Edit Bounty Details' option which brings up a modal for changing Project Type / Permissions.

Definition of Done

• [ ] Allow an ability for the funder to edit the project type and permissions: 'Approval Only' / 'Permissionless' bounties and 'Contest' / 'Cooperative' / 'Traditional' bounties on the issue details page.
• [ ] Design for the experience when contributor(s) have not started on an issue.
• [ ] Design for the experience when a contributor has started on an issue.
• [ ] Update email messaging for the appropriate parties once project types or permissions have been made.
• [ ] Consider the experience of how this issue refreshes in the issue explorer.
• [ ] Make recommendations whether this update should re-sync to the blockchain.
• [ ] Design should take into account responsiveness of the site.
• [ ] Review approach with Gitcoin core team

Additional Information

Open to interpretation on the best solution.

[PixelantDesign]

@willsputra interested?

[gitcoinbot]

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

---

__This issue now has a funding of 200.0 DAI (200.0 USD @ $1.0/DAI) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
  
  
  
  • Want to chip in? Add your own contribution here.
  
  
  • Questions? Checkout Gitcoin Help or the Gitcoin Slack
  
  
  • $25,390.62 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__.

These users each claimed they can complete the work by 4 months, 4 weeks from now.
Please review their action plans below:

1) pinkiebell has been approved to start work.

I would use the 'changeBountyData' method from the contract and emit a bountyChanged event via marketing channels.

Learn more on the Gitcoin Issue Details page.

[pinkiebell]

I missed one crucial thing: One can only the change the bounty data in the 'Draft' stage, not after bounty activation.

Either we implement a user friendly kill & re-issue flow.
or
We do it offchain.

Thoughts?

[owocki]

@pinkiebell this is not a standard bounties change. its a gitcoin change

[pinkiebell]

@owocki
I just looked out for a good solution to reflect the changes via a new ipfs object.
However, this does not work :/.
So I will implement these changes in BountyModel now.

[pinkiebell]

1968 Ready for review (left 2 comments)

[pinkiebell]

@owocki
Btw, would be nice to have ipfs links in the future, so we can follow through 'revisions' of the gitcoin schema. 😄

[owocki]

we have the schemas specs listed at https://github.com/Bounties-Network/StandardBounties/blob/master/docs/gitcoinSchemas.md !

also if you look into your local DB, there IPFS hashes for thecontent blobs are stored in the bounty objects

[pinkiebell]

@owocki
I know, but I mean embedding ipfs object links in the bountyData, so that we can have a list of schemas (added later).

https://ipfs.io/docs/api/#api-v0-object-patch-add-link
https://ipfs.io/docs/api/#api-v0-object-links

[gitcoinbot]

@pinkiebell 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

[pinkiebell]

@gitcoinbot 👍

[gitcoinbot]

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

---

__Work for 200.0 DAI (200.0 USD @ $1.0/DAI) has been submitted by__:

1. @pinkiebell

@vs77bb please take a look at the submitted work:

• PR by @pinkiebell

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $19,529.71 more funded OSS Work available on the Gitcoin Issue Explorer

[PixelantDesign]

@pinkiebell please submit work! Thanks!

[thelostone-mc]

@PixelantDesign good for payout 👍

[gitcoinbot]

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

---

__The funding of 200.0 DAI (200.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @pinkiebell.__

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

[vs77bb]

@pinkiebell Great work 🙂more to come in Ops Excellence channel!