Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

Preventing issue assignment #76

Closed
dustinTopcoder opened this issue Sep 6, 2018 · 2 comments
Closed

Preventing issue assignment #76

dustinTopcoder opened this issue Sep 6, 2018 · 2 comments
Assignees

Comments

@dustinTopcoder
Copy link

dustinTopcoder commented Sep 6, 2018

On one of our projects, a member assigned themselves to some issues before they had a bounty. As such, before we could put the "Open for pickup" label, we had to manually unassign the issues.

Would be nice if the following workflow happened:

  1. When an issue has been edited with a bounty but missing the "Open for pickup" label, prevent anyone from being assigned the issue and clear any previous assignments (reset the issue). If someone attempts to assign themselves, just auto-remove them with a friendly comment about the issue not being ready yet.
  2. When the "Open for pickup" label is added, allow people to assign themselves to the issue.
@jmgasper
Copy link
Collaborator

jmgasper commented Sep 6, 2018

👍

@jmgasper jmgasper self-assigned this Sep 6, 2018
@dustinTopcoder
Copy link
Author

Another thought I had on this. Add a new label called "Not ready". This would be used to tag any issues you wish to have as part of the bounty system, but not ready for pickup yet. So any issue with this label would follow the workflow I put above.

My reasoning is that there are some issues you may have being worked externally and my original idea would not allow that.

jmgasper added a commit that referenced this issue Oct 2, 2018
#89 (major requirement)
#88 (major requirement)
#87 (major requirement)
#86 (major requirement)
#83
#82
#74
#71
#35 (major requirement)
#79 (major requirement)
#76
@jmgasper jmgasper closed this as completed Oct 4, 2018
jmgasper added a commit that referenced this issue Oct 9, 2019
#89 (major requirement)
#88 (major requirement)
#87 (major requirement)
#86 (major requirement)
#83
#82
#74
#71
#35 (major requirement)
#79 (major requirement)
#76
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants