search

ubiquity-os-marketplace / daemon-disqualifier

Follows up on user activities related to task, sends reminders, and unassign inactive users.
0 stars 12 forks source link

Disqualified early #44

Open whilefoo opened 2 hours ago

whilefoo commented 2 hours ago

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 me

Found another issue with the same problem

0x4007 commented 2 hours ago

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:

Whilefoo follow ups will occur after 7 days and disqualification after 14 of no activity.

But these numbers are divided based on the priority level. So for 5 emergency those would be 

7 days / 5 = 1 day 9 hours 36 minutes 
14 days / 5 = 2 days 19 hours 12 minutes

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.