On 29 May 15:27, Dale Scott wrote: > On Thursday, 29 May 2014 16:02:42 UTC-6, Cédric Krier wrote: > > > > On 29 May 12:19, Dale Scott 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. > > > > I think such module will be less powerful than a real issue tracker like > > roundup [1] which is very easy to customize and even link with some > > Tryton data. > > > > [1] http://www.roundup-tracker.org/ > > > > Thanks for the reference Cedric, I'll will take a look at Roundup. > > I would accept less power though, in return for better integration. My > use-case involves designing and building specialized electronics equipment > that is essentially loaned to clients for their temporary use. When an > issue arises with equipment performance (or more commonly, an issue arises > with a sub-component used in the assembly of the equipment for a specific > project), we need to manage the issue in a tracking system, but we are more > interested in answering questions like: On what projects was the part in > question used? When was the part manufactured? When was the part last > re-tested? If it's a design issue (i.e. although a specific serial number > may have been reported in the issue, the root cause of the issue lies with > the component design), what stock was created using the design and where is > the stock now? As you can see, the issue tracker is really a small part of > the whole solution. The effort to integrate a separate tool with Tryton > data may be more work than creating a simple issue tracker from scratch > (maybe?). Also, having to work in two separate environments (Tryton and the > Roundup issue tracker) will make it more difficult for a casual user to get > answers to these questions. Does that make sense?
I don't understand. All the questions you raised are not part of the process of an issue tracker. So I don't see the point of more integration. What will bring an issue tracker like roundup will be to different interface: web, email; the notification; the external users management (with password recovery, email validation etc.). Many things that will take a lot of effort to re-develop in Tryton and which are not really part of the main goal of Tryton. But on an other side, the project module could help to deal with task to perform *inside* the company. So an issue (or many) from the tracker could lead to create one or many task assigned to different people etc. And some kind of automate transition/comment could be done quite easily, see how we linked Mercurial with roundup [1]. [1] http://hg.tryton.org/tryton-tools/file/5f31cfd7e596/hgroundup.py -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
pgpq0VqScNfcs.pgp
Description: PGP signature
