Ilija,
I happy to see that time tracking is a priority for you (and your users). In addition to tracking time associated with a project (or task) I need to track expenses associated with a project or task. For example:
Time Tracking Entry,
Hours; Date; UserName; Client; Project; Task; Note/Comment; $Rate;
Expense Tracking Entry,
Expense; Date; ExpenseType; Description; UserName; Client; Project; $Cost;
I track time at the project level, not the task level. Although I see the need for task level time tracking, it isn't always necessary for small projects.
Thanks!
I happy to see that time tracking is a priority for you (and your users). In addition to tracking time associated with a project (or task) I need to track expenses associated with a project or task. For example:
Time Tracking Entry,
Hours; Date; UserName; Client; Project; Task; Note/Comment; $Rate;
Expense Tracking Entry,
Expense; Date; ExpenseType; Description; UserName; Client; Project; $Cost;
I track time at the project level, not the task level. Although I see the need for task level time tracking, it isn't always necessary for small projects.
Thanks!
MatYadabyte
on Jul 17. 2006. 2:31 pm
I think if your going to do that you need some kind of Project management solution? Any ideas:P
Ilija Studen:Did I miss anything?
Export, ev. import of data?
While importing data from other web-apps (Basecamp was a common request in the forums), the ability to *export* your data may well be a killer feature, IMHO. By giving the possibility to your users to take away their data, you compell them to stay with you (or, in this case, with aC), knowing that whatever comes up at least they can recover their data. You could call this a backup, if you prefer, but it all boils down to the same.
Exporting our data in a big file (probably XML will be most useful here) would be, in my view, essential before calling a release 1.0, although some other great web-apps failed to deliver just this.
What do you think?
Ilija Studen:I'm 100% for the idea that users own their data
Happy to ear that! :)
As for DB dump, of course it works well with phpMyAdmin, but later on (in a production environment, where I'm sure some of us will propose an aC installation to clients, e.g.), a more 'average-user'-friendly way of doing it would be much welcome.
As for myself, I could use the data, as said, as a form of backup or even for moving the content of an aC site from one installation to the other. As you said, a DB dump permits this, but not everybody has access to this or is capable of doing this.
I'm personnally probably not part of the public which could find such a feature interesting, but I'm trying to think from an end-user perspective here. BTW, 'how do I export my data' was the first thing a less web-savvy friend asked me when I showed him off aC. Just thought I woudl share this.
Anyway, aC is already very much usable, and this wouldn't be an essential feature per se, but it could really complement very well a 1.0 release ("look, you can do this, and that, and you have this easy way to check/backup/move your data, so no problem in just trying it out for a while" could be a selling point).
PS: Thank you for your hard and thorough work!
Topic is locked. If you have something important to say about issues discussed on this page please write at hi@a51dev.com.



