A couple of issues relating to manual due date input (the picker's fine):

A couple of issues relating to manual due date input (the picker's fine):

1. I'm a bit puzzled by the format. The manual seems to suggest both dd/mm/yyyy and mm/dd/yyyy work. The former seems to win in case of ambiguity. But an attempted dd/mm/yy gets interpreted as yy/mm/dd.

I find this confusing enough that whenever I manually enter a date I have to check after what date it turned out to be. Any chance of pinning to one (preferably user-chosen) format, and refusing to accept bad input?

2. Relatedly, invalid date input (eg. 45/45/45) results in a 'due date was updated' message, but any due date is removed. I think I'd call that a bug, or at least ambiguous feedback ;)

Comments

  1. Kirill Maximov (KIR)6 November 2016 at 11:41

    Hello, could you please give a specific example when dd/mm/yy gets interpreted as yy/mm/dd?

    As for invalid input - I agree that this is a bug, will add it to our buglist.

    Thanks for the feedback!

    ReplyDelete
  2. Crispin Bennett7 November 2016 at 14:35

    An example would be 01/01/16, which gets interpreted as Jan 16 2001. I think it's the same with any attempt at a 2-digit year.

    ReplyDelete
  3. Kirill Maximov (KIR)7 November 2016 at 22:45

    That's interesting. In my browser such a date is interpreted correctly, as 01.01.2016. Which browser do you use? What timezone you're in?

    ReplyDelete
  4. Crispin Bennett7 November 2016 at 23:13

    That was Safari, but I've just tried it in Chrome with the same result (both on a mac). Timezone is AEST (gmt + 11 currently).

    ReplyDelete
  5. Kirill Maximov (KIR)7 November 2016 at 23:40

    Thanks, will try to fix this.

    ReplyDelete

Post a Comment

Popular posts from this blog

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

Hello friends

Hello friends, We are considering to change behaviour of move up/down command using ctrl+arrows for lists with hierarchy. The new approach is available on our beta site, https://beta.checkvist.com . Could you please try it out and tell us what you think? Thanks! https://beta.checkvist.com
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