1. Mailing Lists
  2. Accounting
  3. Re: [15042] Reasoning on the hr_timesheet_invoice module

Accounting mailing list archives

accounting@odoo-community.org

Browse archives

Re: [15042] Reasoning on the hr_timesheet_invoice module

Re: [15042] Reasoning on the hr_timesheet_invoice module

Avatar

Re: [15042] Reasoning on the hr_timesheet_invoice module

by
InitOS GmbH, Frederik Kramer
- 17/02/2017 10:39:48 
Nhomar, 

no worries, altough we have the same use case over here (nobody ist
perfect ;-) we gonna do it our ownes than. I am not even sure where
to put that change, cause i have the feeling that putting single small
artifacts like his in own modules serves noboday but just created
overhead.

My best to lovely Mexico

No vemos!

Frederik

Am Freitag, den 17.02.2017, 09:23 +0000 schrieb Nhomar Hernandez
[Vauxoo]:
> 
> On Fri, Feb 17, 2017 at 3:07 AM, Frederik Kramer <frederik.kramer@ini
> tos.com> wrote:
> > However, if Nhomar already did it for version 10 i'd rather review
> > a pull request? Nhomar would you sent that umstream to the OCA ?
> Once I migrate my own instance to master I will be preparing some
> PR(s) (for now it is private, but honestly very very easy) once I
> finish my migration and other internal projects I will make a proper
> PR(s)).
> 
> My approach is very specific to my case (but looks so much like what
> Ermin perfectly explained).
> 
> ''''
> The use case is: I have a project for a customer based on time and
> material. As a project manager I see in the timesheets that an
> employee made mistakes and that certain activities took too long and
> I therefore can't fully invoice these activities to the customer
> without getting into troubles or loosing face. Nevertheless these
> activities were done and the cost arised as reported in the
> timesheets by the employee and therefore should be reflected in the
> analytical account.
> 
> ''''
> 
> One thing is my cost analysis (timesheet) and other what I **will
> invoice, which even can be agreed with the customer for hundred of
> reasons.
> 
> As I use that more for reports I put such field and its behaviour
> inside other stuff, that's why for now it is not possible to make a
> proper PR, once I am sure of all the involved stuff I can decide make
> it separate from my development and/or release all the other stuff
> with that toghether.
> 
> ETA: 3 or 4 months.
> 
> Nhomar Hernandez
> CEO Vauxoo.
> Site: http://vauxoo.com
> Twitter: @nhomar
> Blog: http://nhomar.com
> Github User: https://github.com/nhomar
> Odoo Gold Partner
> Skype: nhomar00 (Envia mail previo no lo superviso siempre).
> HangOut: nhomar@vauxoo.com
> Móvil Venezuela:
> +58 4144110269
> Móvil México:
> +52 1 4773933942
> _______________________________________________
> Mailing-List: http://odoo-community.org/groups/accounting-28
> Post to: mailto:accounting@odoo-community.org
> Unsubscribe: http://odoo-community.org/groups?unsubscribe
-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

Reference