kolaente

Thanks for the suggestions!

Default reminders and templates are planned at some point. I also like the idea to be able to view which tasks will remind you in the future.

I think there's an item the backlog for analytics and the archival of individual tasks.

Full text search is hard, especially if it should work with different languages and across different supported database systems.

Would love to discuss the rest further! Especially if you're interested in contributing.

> This isn't so much me saying X feature is a good idea, but to describe what the mismatch was for me between expectation and result.

Gotcha. Thanks for the input!

> I used Crontab (and making it so that you can't open a template twice) to handle scheduling - putting a UI over it - it's been pretty darn good, but crontab also has some serious flaws in it - mostly around things like repeating tasks once every X > 5 days. For hourly/monthly/day-of-month and day-of-week, it works very well though.

Crontab sounds nice but I probably can't give that to someone who has never used it. Still like the idea to use it to handle repeating intervals though.

Your tool sounds nice. Like the sweetspot between "here's a thing I need to do regularly" and the usual habit trackers.

Where did you find that option? I've never heard of any setting like that and I built the thing...

You can filter by label. There's currently no way to do this "on the fly" (which is probably what you're looking for) across lists but you can create a saved filter to search across everything.

Haha yeah pretty much

Do you feel like it's enough to have the system allow for annotation (and maybe visualisation) of the blocking relation? Or would you also want to have a way to let it enforce that relation so that the blocked task cannot be completed until its parent is done?

(Creator of Vikunja here)

Thanks for the in-depth comment!

> But my first impression using this is that it's going to need a lot more work on the depth of the features rather than the breath.

> but when you add little features like that instead of bigger systems, you're going to find that you get lots of people wanting to add new little features to fit their use cases.

Oh definitely. My method until this point was to build a bunch of stuff to a) have what I personally need and b) see what other people need. In this year the focus will be on going deeper on things that work and are actively used. The task detail UX is something like that which needs some work and something I'm not satisfied with. But I can wholly agree with what you said about lots of people wanting to add new little features.

> Imagine having progress that is tied to the number of check boxes I've checked off, something that's not another manual thing that I have to click and keep track of.

The progress option is indeed not great and is likely going away in the future. There is a little circle indicator on a task with the number of total vs done items on a task checklist, similar to how github does it. Is that what you meant?

> Taking my trash out happens every Tuesday. If I were to want to abandon my current system to use this app I would no longer be able to do that.

You can actually do that. It's just not as straight forward as you might think (and that's a problem): you'll need to create a task with a due date of next Tuesday and a repeating schedule of every week / every 7 days.

There has been a bit of debate recently about the repeating option lately with a few good points made so it's highly likely there will be changes to this in the future.

Out of curiosity, what are you building?

As far as I understand it, MIT only requires you to include the attribution next to the binary so ias you guessed next to the source code on the server.

However, the js shipped to clients is usually minified and transformed which means it may count as "compiled" and thus the same rules as for binaries would apply.

Cases like these are the reason why the AGPL exists.