On 23/11/10 17:28 +0100, Udo Spallek wrote: > Hi, > > last days I analyzed the project module and found a - possibly - > unneeded limitation. In project.work is a field 'state' defined with > values 'opened' and 'done'. My requirement is to filter-out all works > with state==done on timesheet.line entry level. But timesheet.line field > 'work' refers to timesheet.work not to project.work where the 'state' > field is defined. > > So I ask me if it is an unneeded limitation that 'state' field is > limited to project.work and not to the more general timesheet.work? For > me, each imaginable kind of work may have the states 'opened' and > 'done'. > > If there are good reasons to have the 'state' field on project.work > instead of timesheet.work, what is the best way to replace the field > 'state' on project.work from a custom module? > > Is there a better way to /disable/ the 'state' field on level of > project.work, and /enable/ it on timesheet.work level?
I think you should use the active field to prevent any more timesheet encoding on a work. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpuXfZo0N9jA.pgp
Description: PGP signature
