Task grouping by project
This would be so much easier than adding new tags to distinguish them. I could also make sharing tasks easier -- just share out all tasks in a project to the same set of users. Reporting, likewise, could see some simplification with the addition of project-based organization.
Tags as a catch-all heirarchy solution started off as a good idea, but as the site as grown and I’ve learned more about SlimTimer user usage patterns I now see a place for “supertags” or explicitly defining concepts like Project and Billable v Non-billable tasks. I’ll have more on this soon.
Jost Langenfeld commented
I like the simple 2 dimensional structure (task/tag). Would love to see a tag cloud to the right of the edit task screen for quick filtering
Is this still planned?
This is amazingly simple and ready to use. I started right away soon after i came to know about this product in the Sunday Magazine (today).
I entirely agree that a couple of more 'tags' or fields would be of great help.
been using slimtimer for long time now, but it appears as if this is more or less dead with no new developments? As an alternative I found toggl which provides all these features that have been suggested for years.
Google Code hosting's Issues list has an awesome implementation of tags. It allows you to require that one tag that starts with status-(out of status-planned, status-finished for example) be selected.
Mathieu Dumoulin commented
We need ways to group and share tasks more easily around the office, for example, with all my employes. I get tired of creating a task and sharing it with everyone and i have only 2 other employes. Getting 2 more soon looks like a pain more than a joy!
I know that user hierarchy is not planed ok, but being able to say who is in what team to share all the tasks around these is really a must. Wathever the way will be, we definitely need this.
Ines Lejarraga commented
It would be nice to be able to scroll through existing tags when entering them in. This way you don't inadvertently add new ones that are intended to be the same as existing ones. Thereby further increasing the long list
I would find this feature most useful if the tasks were actually grouped under their project headings in the list; i.e. a simple heirarchy. I'm happy to use tags for projects for most purposes, but I feel that the interface can get a bit unweildy once you've got quite a few tasks listed, so I think I'd mainly use the projects feature for visual grouping (if that's how you implemented it).
Right now, I treat my tasks as Projects instead and time based on each project instead of individual tasks. I started doing this because I was more familiar with products like XTT that did it this way.
I would definitely like to be able to add tasks under a Project or some sort. But also have default tags for tasks under those projects (billable and non-billable for respective projects, etc).
This helps thanks
this really would allow people who are familiar with and use basecamp to also bring slimtimer into their work flow. ... because basecamp uses projects/tasks hierarchy. It would also be really cool if you could import tasks/projects from basecamp's rss feeds into slimtimer... making things just a little bit faster to manage/enter in.
I think I could live with using tags for hierarchy if we could do a better job using them. I'd like to pick some tags that would group tasks in the Timer. For example, if I have a few tasks with the "Project X" tag and a few with the "Project Y" tag, I'd like to see a collapsible group for the "project X" and "Project Y" in the timer. That way I can limit the list to the project i'm on.
Why would it be easier than tags? Instead of a big bunch of tags you would have a big bunch of projects - I'm not sure I see where the benefit lies. If a task belongs to Project X, give it a tag 'Project X', then you can run reports for just that tag. Easy. If you want to share all tasks belonging to 'Project X' with other users, you can do that with tags too.
The FAQ on http://slimtimer.com/help#faq_tasks states that "The concepts [users, customers, and projects] don't exist here. I don't believe in imposing a rigid hierarchy [...] You determine [details] on an individual task basis. You use tags to create a reporting hierarchy that works for you."
I like your suggestion. I just want to note that there have been hints (I think it was in the blog) that SlimTimer is intended to be a lightweight, project-less tool and that there would come a bigger project-able tool (with a fee).