Menu
▾
▴
tsheetx-developers
|
From: Denis C. <2n...@ak...> - 2011-08-19 13:45:05
|
Hi, Looking on the web for a good solution to implement a timesheet solution in my company I came across your project (the old version at first then found the Next Gen one). One minor caveat of the current solution to my taste was the lack of possibility to automatically add a set of tasks to a newly created project, therefore I looked in the code and implemented that feature (including the configuration entry to set the tasks labels). That seems to work nicely for me and I'd be more than happy to send you the updated package so it can be included in a future release, I've updated the project creation logic as well as configuration page & action and the database model so the default stays on "Default Task". Don't hesitate to let me know if you're interested, I've got all that right at hand. Regards, Denis |
|
From: Scott M. <sco...@gm...> - 2011-08-20 19:54:34
|
Denis, I've been unable to work on the project for a while, but I know this was one of the areas that several people have been interested in fixing. So, yes, I think it's safe to say we would like to see what you've added to the project. -Scott L. Miller On Fri, Aug 19, 2011 at 8:32 AM, Denis Carniel <2n...@ak...>wrote: > Hi, > > Looking on the web for a good solution to implement a timesheet solution in > my company I came across your project (the old version at first then found > the Next Gen one). > > One minor caveat of the current solution to my taste was the lack of > possibility to automatically add a set of tasks to a newly created project, > therefore I looked in the code and implemented that feature (including the > configuration entry to set the tasks labels). > > That seems to work nicely for me and I'd be more than happy to send you the > updated package so it can be included in a future release, I've updated the > project creation logic as well as configuration page & action and the > database model so the default stays on "Default Task". > > Don't hesitate to let me know if you're interested, I've got all that right > at hand. > > Regards, > Denis > > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > |
|
From: Peter L. <pal...@gm...> - 2011-08-21 00:30:25
|
Hi Denis, I have already coded a standard tasks function. It is to be found in the txsheet-2.0-demo branch. The code there includes a form to add and delete standard tasks to the standard task table. And in the add task form, I list out the standard tasks that can be chosen to be added to a project. The code is ./tsx/tasks/task_add_std.php, ./tsx/tasks/task_std_action.php, and ./tsx/tasks/task_add.php I would like to look at what you have implemented, and we can agree to merge code, or select appropriate features from both sets to improve TSNG. Peter On 08/19/2011 11:32 PM, Denis Carniel wrote: > Hi, > > Looking on the web for a good solution to implement a timesheet solution in my company I came across your project (the old version at first then found the Next Gen one). > > One minor caveat of the current solution to my taste was the lack of possibility to automatically add a set of tasks to a newly created project, therefore I looked in the code and implemented that feature (including the configuration entry to set the tasks labels). > > That seems to work nicely for me and I'd be more than happy to send you the updated package so it can be included in a future release, I've updated the project creation logic as well as configuration page& action and the database model so the default stays on "Default Task". > > Don't hesitate to let me know if you're interested, I've got all that right at hand. > > Regards, > Denis > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers |
|
From: paul c. <pdc...@bl...> - 2011-08-21 06:54:15
|
is there some crossover between this and the 'clone user' stuff. For that , you need to set up one user and then can copy all the tasks across to another. Coming at the same problem from the other end ? On 21/08/11 01:30, Peter Lazarus wrote: > Hi Denis, > I have already coded a standard tasks function. It is to be found in the > txsheet-2.0-demo branch. The code there includes a form to add and > delete standard tasks to the standard task table. And in the add task > form, I list out the standard tasks that can be chosen to be added to a > project. The code is ./tsx/tasks/task_add_std.php, > ./tsx/tasks/task_std_action.php, and ./tsx/tasks/task_add.php > > I would like to look at what you have implemented, and we can agree to > merge code, or select appropriate features from both sets to improve TSNG. > > Peter > > On 08/19/2011 11:32 PM, Denis Carniel wrote: >> Hi, >> >> Looking on the web for a good solution to implement a timesheet solution in my company I came across your project (the old version at first then found the Next Gen one). >> >> One minor caveat of the current solution to my taste was the lack of possibility to automatically add a set of tasks to a newly created project, therefore I looked in the code and implemented that feature (including the configuration entry to set the tasks labels). >> >> That seems to work nicely for me and I'd be more than happy to send you the updated package so it can be included in a future release, I've updated the project creation logic as well as configuration page& action and the database model so the default stays on "Default Task". >> >> Don't hesitate to let me know if you're interested, I've got all that right at hand. >> >> Regards, >> Denis >> >> >> ------------------------------------------------------------------------------ >> Get a FREE DOWNLOAD! and learn more about uberSVN rich system, >> user administration capabilities and model configuration. Take >> the hassle out of deploying and managing Subversion and the >> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 >> _______________________________________________ >> Tsheetx-developers mailing list >> Tsh...@li... >> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers |
|
From: Peter L. <pal...@gm...> - 2011-08-22 22:37:44
|
Paul, that's an interesting suggestion. Being able to selectively copy tasks from one project to another. I will add it to my todo list. Peter On 08/21/2011 04:54 PM, paul cooper wrote: > is there some crossover between this and the 'clone user' stuff. For > that , you need to set up one user and then can copy all the tasks > across to another. > Coming at the same problem from the other end ? > > |
|
From: Peter L. <pal...@gm...> - 2011-08-22 22:46:24
|
Hi All, I have added definitions for three new tables, std_tasks, expense, and category. The first provides a table for keeping a list of standard tasks which can be selectively added to any project. The latter two are for some basic new function to track expenses. Also, there are three new authorisation levels to help manage access to expenses, which have been defined in the config table. You can find the definitions in the timesheet.sql.in file or in the timesheet_upgrade_to_1.5.3.sql.in file. Peter |
|
From: David T. <tom...@us...> - 2011-08-25 11:47:27
|
Back on the list... I think "no/any client" is handled ok, I have set up an install with clients turned off completely. Default project and default task worry me. Do we really need these? It gets confusing when times are entered against them. Dave Date: Wed, 24 Aug 2011 19:31:48 +1000 From: pal...@gm... To: tom...@us... CC: ma...@rw...; 2n...@ak...; sco...@gm... Subject: Re: [Tsheetx-developers] Customizable default tasks David, what are you referring to in special handling of defaults? Do you mean that a default task, project, client are currently inserted in the database and show up in lists? Peter On 08/24/2011 06:08 PM, David Thompson wrote: Peter Without looking at the code, but from your good analysis, I agree that your suggestion is better. Scott was working on a new config style (in the V2 branch?) anyway, so extending the old config table that is earmarked for removal is not useful. So a good design sounds something like you said: a set of (potential) standard tasks, that can be checkboxed when creating tasks in a project, together with a UI to manage that list of standard tasks (add, delete, modify). Can we also get away from special handling of defaults here (default task, default project, no/any client)? Cheers Dave |
|
From: Peter L. <pal...@gm...> - 2011-08-25 12:10:25
|
I don't like these default things either. Will investigate. On 08/25/2011 09:47 PM, David Thompson wrote: > Back on the list... > > I think "no/any client" is handled ok, I have set up an install with > clients turned off completely. > Default project and default task worry me. Do we really need these? It > gets confusing when times are entered against them. > > Dave > > ------------------------------------------------------------------------ > Date: Wed, 24 Aug 2011 19:31:48 +1000 > From: pal...@gm... > To: tom...@us... > CC: ma...@rw...; 2n...@ak...; > sco...@gm... > Subject: Re: [Tsheetx-developers] Customizable default tasks > > David, > what are you referring to in special handling of defaults? Do you mean > that a default task, project, client are currently inserted in the > database and show up in lists? > Peter > > On 08/24/2011 06:08 PM, David Thompson wrote: > > Peter > Without looking at the code, but from your good analysis, I agree > that your suggestion is better. Scott was working on a new config > style (in the V2 branch?) anyway, so extending the old config > table that is earmarked for removal is not useful. > > So a good design sounds something like you said: a set of > (potential) standard tasks, that can be checkboxed when creating > tasks in a project, together with a UI to manage that list of > standard tasks (add, delete, modify). > > Can we also get away from special handling of defaults here > (default task, default project, no/any client)? > > Cheers > Dave > |
|
From: Scott M. <sco...@gm...> - 2011-08-25 14:54:11
|
I believe the default task, project and client entries were created as a solution to the problem of "how should the system handle a user that has no clients, projects or tasks?". This particular answer meant the system didn't have to handle that problem as there should never be a time when a user didn't have at least one of each. FWIW, I dislike them as well, and I'm hopeful that they can be removed. -Scott On Thu, Aug 25, 2011 at 7:10 AM, Peter Lazarus <pal...@gm...> wrote: > I don't like these default things either. Will investigate. > > On 08/25/2011 09:47 PM, David Thompson wrote: > > Back on the list... > > I think "no/any client" is handled ok, I have set up an install with > clients turned off completely. > Default project and default task worry me. Do we really need these? It gets > confusing when times are entered against them. > > Dave > > ------------------------------ > Date: Wed, 24 Aug 2011 19:31:48 +1000 > From: pal...@gm... > To: tom...@us... > CC: ma...@rw...; 2n...@ak...; > sco...@gm... > Subject: Re: [Tsheetx-developers] Customizable default tasks > > David, > what are you referring to in special handling of defaults? Do you mean that > a default task, project, client are currently inserted in the database and > show up in lists? > Peter > > On 08/24/2011 06:08 PM, David Thompson wrote: > > Peter > Without looking at the code, but from your good analysis, I agree that your > suggestion is better. Scott was working on a new config style (in the V2 > branch?) anyway, so extending the old config table that is earmarked for > removal is not useful. > > So a good design sounds something like you said: a set of (potential) > standard tasks, that can be checkboxed when creating tasks in a project, > together with a UI to manage that list of standard tasks (add, delete, > modify). > > Can we also get away from special handling of defaults here (default task, > default project, no/any client)? > > Cheers > Dave > > > |
|
From: Peter L. <pal...@gm...> - 2011-08-25 21:53:59
|
I haven't looked at the code yet. The situation could simply be handled by saying: no tasks, no projects. But then additional code could be needed in some sql selects to ignore incomplete clients and projects. Perhaps that;s prefereable to forcing the addition of a project when creating a client, or jumping to add new task just after a new project is created. Peter On 26 August 2011 00:54, Scott Miller <sco...@gm...> wrote: > I believe the default task, project and client entries were created as a > solution to the problem of "how should the system handle a user that has no > clients, projects or tasks?". This particular answer meant the system > didn't have to handle that problem as there should never be a time when a > user didn't have at least one of each. > > FWIW, I dislike them as well, and I'm hopeful that they can be removed. > > -Scott > > > On Thu, Aug 25, 2011 at 7:10 AM, Peter Lazarus <pal...@gm...>wrote: > >> I don't like these default things either. Will investigate. >> >> On 08/25/2011 09:47 PM, David Thompson wrote: >> >> Back on the list... >> >> I think "no/any client" is handled ok, I have set up an install with >> clients turned off completely. >> Default project and default task worry me. Do we really need these? It >> gets confusing when times are entered against them. >> >> Dave >> >> ------------------------------ >> Date: Wed, 24 Aug 2011 19:31:48 +1000 >> From: pal...@gm... >> To: tom...@us... >> CC: ma...@rw...; 2n...@ak...; >> sco...@gm... >> Subject: Re: [Tsheetx-developers] Customizable default tasks >> >> David, >> what are you referring to in special handling of defaults? Do you mean >> that a default task, project, client are currently inserted in the database >> and show up in lists? >> Peter >> >> On 08/24/2011 06:08 PM, David Thompson wrote: >> >> Peter >> Without looking at the code, but from your good analysis, I agree >> that your suggestion is better. Scott was working on a new config style (in >> the V2 branch?) anyway, so extending the old config table that is earmarked >> for removal is not useful. >> >> So a good design sounds something like you said: a set of (potential) >> standard tasks, that can be checkboxed when creating tasks in a project, >> together with a UI to manage that list of standard tasks (add, delete, >> modify). >> >> Can we also get away from special handling of defaults here (default task, >> default project, no/any client)? >> >> Cheers >> Dave >> >> >> > |
|
From: Peter L. <pal...@gm...> - 2011-08-25 22:49:55
|
Just experimenting with tsng. I created a new client. Client appears in client lists,and doesn't appear in any drop down lists I created a new project for this client. a default task gets created as well. Delete the default task, and the project list says "no tasks". Try to add some time to this project, and the task list says "no tasks assigned to you" So it seems that tsng already handles the situation where there are no default tasks or projects. Just need to delete the code that creates the defaults in the first place and test using an empty database. Peter On 08/26/2011 12:54 AM, Scott Miller wrote: > I believe the default task, project and client entries were created as > a solution to the problem of "how should the system handle a user that > has no clients, projects or tasks?". This particular answer meant the > system didn't have to handle that problem as there should never be a > time when a user didn't have at least one of each. > > FWIW, I dislike them as well, and I'm hopeful that they can be removed. > > -Scott > > On Thu, Aug 25, 2011 at 7:10 AM, Peter Lazarus <pal...@gm... > <mailto:pal...@gm...>> wrote: > > I don't like these default things either. Will investigate. > > On 08/25/2011 09:47 PM, David Thompson wrote: >> Back on the list... >> >> I think "no/any client" is handled ok, I have set up an install >> with clients turned off completely. >> Default project and default task worry me. Do we really >> need these? It gets confusing when times are entered against them. >> >> Dave >> >> ------------------------------------------------------------------------ >> Date: Wed, 24 Aug 2011 19:31:48 +1000 >> From: pal...@gm... <mailto:pal...@gm...> >> To: tom...@us... >> <mailto:tom...@us...> >> CC: ma...@rw... <mailto:ma...@rw...>; >> 2n...@ak... <mailto:2n...@ak...>; >> sco...@gm... <mailto:sco...@gm...> >> Subject: Re: [Tsheetx-developers] Customizable default tasks >> >> David, >> what are you referring to in special handling of defaults? Do you >> mean that a default task, project, client are currently inserted >> in the database and show up in lists? >> Peter >> >> On 08/24/2011 06:08 PM, David Thompson wrote: >> >> Peter >> Without looking at the code, but from your good analysis, I >> agree that your suggestion is better. Scott was working on a >> new config style (in the V2 branch?) anyway, so extending the >> old config table that is earmarked for removal is not useful. >> >> So a good design sounds something like you said: a set of >> (potential) standard tasks, that can be checkboxed when >> creating tasks in a project, together with a UI to manage >> that list of standard tasks (add, delete, modify). >> >> Can we also get away from special handling of defaults here >> (default task, default project, no/any client)? >> >> Cheers >> Dave >> > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X