• As a user, I want to be able to create a bounty once and have it available for an indefinite period for claimants. This is because I want my bounty to be a recurring task that doesn’t change often.

• Creator starts the bounty create process

• Provides bounty details

• Passes optional flag “Make this bounty evergreen?”
In the web UI: provide an explanation or tooltip
In the discord bot, simply provide a flag

• Assuming from here the flag is selected

• When the bounty is claimed:
Check the existence of the flag
When claimed, do not claim the original bounty, instead POST a new bounty directly to In Progress with the following data:
Indicate evergreen with a boolean flag
Indicate parent or child
If parent: list child Ids
If child, list parent Id
// parent
evergreen: true,
isParent: true,
children: [
	0x3445, 0x54949, 0xffff,
]


// child
evergreen: true,
isParent: false,
parentId: 0x457ABC
Add a message to the “Bounty Claimed” notification
“...as you marked this bounty as evergreen it will stay on the board as Open. We’ve created a separate bounty automatically for you and <user> to collab on - LFG! <bountyId>”
 

• The creator at any time should be able to Remove or Edit the evergreen bounty
Fields should be restricted, it should not be possible to edit away the evergreen status
Child evergreen bounties should not be editable (which is fine because they’re not in the Open state)
Deleting the parent should move it to a Closed state, we should make it clear that any active children will still be running

• Ability to edit/delete bounties (API Auth)

• Add evergreen fields to bounties schema (S)

• Add evergreen flag to bounty create workflow (XS)

• Add the evergreen check in the bounty claim workflow (XS)

• Trigger the bounty create functionality if an evergreen bounty is claimed (M)

• Amend user messaging on discord if evergreen bounty detected (S)

• Integrate Edit evergreen features into discord and Web UI (M)

• Add evergreen tests - API (S)

• Add evergreen tests - Discord (L)*

/

• Submit and Completed actions are taken in DMs with the Bounty Bot.

• All that remains on the Bounty Board are open bounties. Once a bounty is claimed or all available claims of an evergreen bounty are exhausted, it is removed from the Bounty Board channel.

• As a user, I want to be able to have multiple people apply for my bounty before it is moved into a ‘claimed’ state. This is because users are prone to spamming the claim button and I want to give the right person for the job time to apply for the bounty.

• Bounty creator adds the flag allow multiple people to apply for this bounty? - I’d argue this should be default.

• The claim button then doesn’t move the bounty from Open → In Progress, instead, the user is prompted to add a message to the creator (either Discord DMs or Web UI)

• The creator receives a notification that “[they] have a new claimant (total X claimant(s)), here is what <user> wrote: I love you ”

• The creator should be able to “view claimants” when looking at the bounty, which will pull up:
Discord: could or should potentially just direct the user to the web UI
UI: list of options, just click a button to confirm

• Once confirmed, move selected claimant to the “claimed” and progress the flow as normal.

• For backwards compatibility, we add fields to the schema:

claimants: Array<Claimant extends DiscordUser { message: string }>;
allowMultipleClaims: boolean;

• Claimants will appear if allowMultipleClaims is set to true

• Claimants will contain the user details, and the message they sen

• Add claimants to the schema (S)

• Add a prompt for the user to add a message when claiming (S)

• Add the message alongside the claimant in an array and update the schema (S)

• Amend the frontend to show the claimants and messages (M)

• Allow creators to select a claimant from this list (S)

• Once selected, move one of the claimants into “claimed by” (S)

• A way for project managers to quickly note a bit of good work done and a planned reward amount.

• Puts together a private list of virtual IOUs. List is private to the owner, but a future phase may allow for notifying the subject

• Need a way to resolve the IOUs - delete? Mark done?

/iou description: <what it is for> owed-to: <user> reward: <bank>

/iou list list-type: unpaid

/iou list list-type: paid

/iou paid iou-id: <id> note: <optional note>

/iou delete iou-id: <id> note: <optional note>

• Need to handle messaging correctly (discordMessageId and other message objects)

• Validate /bounty commands to prevent invalid commands and options for IOUs (claim/submitted/apply/assign )

• Need to handle lack of a due date?