Hi Florian, My personal opinion on this would be that this is a customization that is probably better not to introduce directly to the framework. Probably many customers require many different variations on billing. So this is a place where an infinite amount of variations can happen right?
So I would suggest to you to work on SECAs to wire up the invoicing to your liking. This is the easiest way I can think of that has minimal intervention on the code without digging into too much detail. I hope this is useful. Regards, On Wed, Jul 13, 2016 at 12:07 PM, Montalbano Florian < [email protected]> wrote: > Hi all, > I have a client who wants only one invoice for the several projects we > have with him. > So, I'm trying to create an invoice from the hours spent on a project > managed in the "Project" component and from the hours spent on a project > managed in the "Scrum" component. > > On the one hand, the billing from the two components seems close and I was > wondering if there was a way to create a project including the two other > (as sub-project) to then bill all the hours registered in the same invoice. > > On the other hand, it feels like the client asks for something not that > standard with this and maybe I should find a way to "merge" the two > invoices instead. > > What are you thoughts on this subject ? > > Thanks, > Have a nice day, > > Florian Montalbano > >
