Hi,
Ciaran, I didn't know whether I would be able to mention Quest and my past involvment with you, so I've been holding back a bit...
I think it would be a very good idea to setup a common codebase with your enhacements and some future extensions. However, I see one important issue that the Quest WF contains some customizations that wouldn't be compatible with a general purpose WF.
Also, ]po[ would have to use the WF attached to several object types in addition to "tickets", including im_project, im_invoice and im_company.
So one of the most important next steps would be to identify the common functionality, "factoring it out", putting it into a clean package and converting all extensions into extension packages. I know that this can be quite a painful process once you've got some customers running the code in production use...
How do you see this?
Bests,
Frank
