-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disqualified early #44
Comments
Perhaps we should remove the concept of "deadlines" because we care more for persistent effort on a project vs a hard deadline date (some projects are underestimated for example) It could be helpful to make it transparent what the disqualifier dates will be, for example:
But these numbers are divided based on the priority level. So for 5 emergency those would be
Also note that currently our settings are 3.5 days and 7 but I think we should do 7 and 14 with this new behavior. Let's change the assign message start to at least remove the concept of "deadlines" Perhaps on the assign event, this plugin can leave a comment explaining the schedule. Then we can remove the start message on that plugin. |
/start |
Tip
|
Need some clarification here..
|
Passed the deadline and no activity is detected, removing assignees: @ariesgun. |
This is the issue where I got disqualified 3 days earlier than the deadline
When I started the task with
/start
on 28th October, the bot said the deadline is Sat, Nov 2, 2:36 PM UTC, however on 30th October, the bot said the deadline has passed and unassigned meFound another issue with the same problem
The text was updated successfully, but these errors were encountered: