Any Toggl users here? I'm putting together an integration so the toggl (Chrome extension) button ( https://github.com/toggl/toggl-button ) is displayed for tasks on a Checkvist list. It's dead simple (a few lines of javascript), but I'm slightly torn on the best way to handle one aspect: whether or not toggl is shown for a particular list. It can't be always-on, as it adds too much clutter for non-projecty lists (who wants a timer button for the carrots on their grocery list?). What I have now is that if any task on a list is tagged #toggl, then all tasks on that list will have the toggl button. A few alternatives I canvassed were: - display toggl buttons only on subtasks of a task tagged with #toggl - display toggl buttons only on focused (hoisted) tasks - find some other way to indicate that all of a list's tasks should have the button, eg. something encoded in the list's name I think what I have now is the most convenient of these (I don't want to hav...
Unfortunately, it is not possible.
ReplyDeleteYou can vote for checkvist.uservoice.com - Move notes up and down within task or use sub-items instead of notes in the meantime.
You can also use multi-line notes, if this suits you, and re-arrange text there.
Yep have voted thanks.
ReplyDeleteOne of the strengths of Checkvist is its power to rearrange items. Notes are not in this mindset. They can't be reordered, they can't be moved to other tasks, they can't be edited by other collaborators, they don't go away when their text is deleted. Notes have their place, but cloud be more useful (in the sense of easier to use) for me.
ReplyDeleteSince the introduction of time tags, I'm using more note instead of subtasks, because they don't invalidate the time entries (with the setting that a task depends on its subtasks). This isn't feeling quite right yet.
ReplyDeleteNotes are not intended to be used as sub-items, they are rather comments (bad naming). We don't keep the order of notes in the database, they are ordered by timestamp - so changing notes behaviour is a heavy task.
ReplyDeleteBy the way, I don't quite understand how sub-tasks invalidate time entries. On the beta.checkvist.com, the behaviour of time tags should not depend on the dependency setting - we've fixed it, I believe.
Right, on beta it's fixed. Thanks.
ReplyDelete