Recurring tasks are not handled as expected.

Recurring tasks are not handled as expected.

If I complete a recurring task, the expected behavior is that the due date is changed to the next due date. But this is not working. Also reloading the page and clearing the browser cache has no effect.
The completed task is still displayed (stroked out) with the old due date.


Is this a bug?

Comments

  1. Mark Dickens21 April 2018 at 13:07

    Hi Frank Arnold ... my understanding is that the repeat of a recurring, just completed task is not handled in the browser, it is occurs server-side ... there is some control over how far in advance the new repeat appears though.

    It’s not instantaneous in the browser

    ReplyDelete
  2. Frank Arnold21 April 2018 at 13:16

    Hi Mark Dickens Yes, this is handled on the server in the background and not in the browser. But if a task is completed, the next date should be set instantly (ajax request in the background to update the record in the database on the server and reflect this in the browser)

    I would say this is a bug.

    ReplyDelete
  3. Kirill Maximov (KIR)21 April 2018 at 14:02

    Hi, the next due date for completed repeating tasks is set once per hour (unless there is a specific "Generate" setting in the repeating due dialog).
    Is such behaviour a problem?

    ReplyDelete
  4. Frank Arnold21 April 2018 at 14:15

    Hi, yes this is confusing and gives the feeling that something is not working correctly.
    If a task is completed and has a recurring date, the task should not displayed as "completed" with the old invalid due date. This should be updated instantly

    ReplyDelete
  5. Frank Arnold21 April 2018 at 15:42

    Btw.. also this setting once per hour is not working...
    "closed by Frank Arnold | yesterday at 21:34" and now it's 00:36 and the item has still the old due date after reloading.

    ReplyDelete
  6. Xavier B21 April 2018 at 19:19

    I agree, I always thought that "cd" should simply set the next recurring date on a task. Perhaps we need a new "nd" (next date/due?) that would increment the due date on a given item by the recurring interval. That'd be great!

    ReplyDelete
  7. Mark Dickens22 April 2018 at 01:47

    Frank Arnold agreed that sounds like a bug ... I wouldn’t dream of asking if you’re sure you have an internet connection! 😀

    ReplyDelete
  8. Frank Arnold22 April 2018 at 01:57

    Mark Dickens :D
    The recurring task is still not updated to the next due date after one day... so yes, this is a bug.

    ReplyDelete
  9. Kirill Maximov (KIR)22 April 2018 at 05:50

    Hello, Frank Arnold, could you please focus on the problematic item with shift+right and send the resulting URL to kirsa@checkvist.com for the investigation. Thanks!

    ReplyDelete
  10. Kirill Maximov (KIR)22 April 2018 at 06:28

    Hello Frank Arnold, the matter is that the due date you've set is still in the future, May, 1. Given that this date has not passed yet, the task remains closed, indicating that no action should be taken from your side so far. After May, 1, it will be re-opened and the next due will be set.

    Does it make sense?

    ReplyDelete
  11. Frank Arnold22 April 2018 at 06:42

    Kirill Maximov This is IMO not the best implementation.
    A recurring completed task with a due date in the future, must be handled as completed at the due date. So instead of leaving the state of the task as completed, the next due date must be set and the task must be opened again (so it's visible somewhere in the "due" tab for next month/next year etc).
    Btw. this is also how it works in all other apps like Todoist, RTM etc. Thats why I'm a bit confused about the behavior with Checkvist.

    ReplyDelete
  12. Jim McGuire22 April 2018 at 09:14

    I'm very comfortable with the way this works now, in fact, I would be unhappy with it changing to reflect the way Frank Arnold would like it to work. I am pleased that recently completed tasks now are not visible on my "Due" radar, at least not until the chosen time to regenerate the task is reached. There does seem to be more than one way to do things.

    ReplyDelete
  13. Frank Arnold22 April 2018 at 10:45

    Btw, this is how it's handled by Asana (I quote the description I've got from the Asana support):
    "When you as set a task to recur (https://asana.com/guide/help/tasks/fields#gl-recurring-tasks), you are telling Asana to duplicate that task when it is marked complete and to set the due date on the new task to be a certain interval of time after the due date on the previous task...

    Its important to note that this duplication happens at the exact time you mark your task as complete"

    It works exactly the same also in Todoist, Remember The Milk etc.. and completely different in Checkvist.

    ReplyDelete
  14. Kirill Maximov (KIR)25 April 2018 at 22:40

    Hello Frank Arnold, in Checkvist recurring tasks are not duplicated. Still, we can add an option to reopen the task immediately with the new due date. I've created a request in UserVoice for it, please vote/watch: checkvist.uservoice.com - Add an option to reopen completed repeating due task without waiting for the due date to come

    ReplyDelete

Post a Comment

Popular posts from this blog

Hello friends

Hello friends, Recently we've got a request to introduce a shortcut to move items to the first/last position on the current level of hierarchy: https://checkvist.uservoice.com/forums/2121-general/suggestions/15758854-shortcut-to-send-an-item-at-the-top-of-the-current And this bring me to a thought to use the current shortcut (Ctrl+Home/Ctrl+End) for this purpose. But with an extension - if an item is already on the top position on the current hierarchy level, Ctrl+Home would move item one level up (and put it at the beginning of this level). This will break the current behaviour (moving item to the beginning of the list), but probably will make this shortcut more useful. What do you think? https://checkvist.uservoice.com/forums/2121-general/suggestions/15758854-shortcut-to-send-an-item-at-the-top-of-the-current
Read more

Hello friends!

Hello friends! I'd like to ask for your opinion regarding multi-line text editing. This suggestion comes from one of our Russian-speaking customers Dolina Zamkova so here is a translated abstract of our email conversation. Current problem: When you write multi-line text, you must press 'Shift-Enter' first, then use 'Enter' to start a new line, then 'Ctrl-Enter' to submit the text. Wouldn't it be easier to have a setting that will allow using Enter to always write multi-line texts, and always submit on 'Ctrl-Enter', like you do it in text messengers? So we could add a new account-wide setting, on the Settings page: () Finish editing by pressing 'Ctrl-Enter' (convenient for multi-line text) What do you think? Do you write multi-line texts in Checkvist at all? Other thoughts of how we could make it better? :)
Read more

I'm really enjoy using checkvist, you are adding great features very quickly.

I'm really enjoy using checkvist, you are adding great features very quickly.  What I feel is missing is more use cases.  How are people using Checkvist?  What are some recommend workflows?  How many lists do you have? User Stories will not only help those of use already using Checkvist to be more effective, but attract more non-technical customers. I like to keep my lists at a minimum.  I only split out for sharing but I'd prefer not to. Here are my lists: * Inbox:  This is where zapier based integrations go.  I have Jira tickets and emails tagged with "!action" going to list which I process daily. * The List:  This is my primary list.  Everything is here.  I use sub-nodes for different areas. * Honey Do:  This is the list my wife and I share to make sure we know what we both want done around the house. * "Client Project" - I have a few Lists I share with clients (Free lance web developer). I"m looking to write a more detailed blog post. How are your l
Read more