On Thursday, 29 May 2014 22:51:35 UTC-6, Albert Cervera Areny wrote: > > 2014-05-30 6:34 GMT+02:00 Sharoon Thomas <[email protected] > <javascript:>>: > >> >> On May 30, 2014, at 12:49 AM, Dale Scott <[email protected] >> <javascript:>> wrote: >> >> I am in need of an "issue tracking system" integrated with Products >> (referencing a specific product), Stock (referencing a specific lot or >> serialized item), and Projects (referencing a specific project). Does >> anyone know of an existing module that could be used? A more generalized >> module would also be suitable, e.g. also integrating customers, vendors, >> sales orders, purchase orders, shipping orders, etc. >> >> >> We have extended project management module of Tryton to do this for us >> and we have a web app built around it. >> We are a software development shop and the issues are obviously tasks, >> bugs etc. >> However, we also know users who use it for other purposes like the ones >> you mentioned. >> >> You can see some documentation with screenshots [1]. >> The design is completely extensible and you can adapt it to do the >> additional integrations with sales etc you are talking about. >> > > We have also created several small modules extending projects and tasks > for our own needs [1]. We're not using Nereid Project yet, but I think we > should try it soon.. > > [1] https://bitbucket.org/nantic/profile/repositories?search=project > Thanks Albert, I will take a look. I can understand the value in extending projects and tasks, but I wonder if an issue needs to be a "first-order citizen" in Tryton, so it can bring together other "first-order citizens", such as projects, products (design or specifications), stock (serial number of real physical items), perhaps sales (or perhaps a sale is a "second-order citizen", and an issue references a sale through the serial number on a sales or delivery order?), and other "first-order citizens" (if the metaphor is valid, and there are others). Does this make sense?
Dale
