This repository was archived by the owner on Mar 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Preventing issue assignment #76
Comments
👍 |
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
to topcoder-archive/topcoder-platform-topcoder-x-processor
that referenced
this issue
Oct 2, 2018
topcoder-archive/topcoder-platform-topcoder-x-ui#89 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#88 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#87 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#86 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#83 topcoder-archive/topcoder-platform-topcoder-x-ui#82 topcoder-archive/topcoder-platform-topcoder-x-ui#74 topcoder-archive/topcoder-platform-topcoder-x-ui#71 topcoder-archive/topcoder-platform-topcoder-x-ui#35 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#79 (major requirement) topcoder-archive/topcoder-platform-topcoder-x-ui#76
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
The text was updated successfully, but these errors were encountered: