Thanks - they do work together; for example each ticket is linked to one requirement. I'm just wondering how to scale it:
component is part of a project requirement applies to one component ticket addresses one requirement test plan written for each ticket multiple test steps per test plan multiple test step entries per test step multiple test run results per test plan and so on. This would make for one large project management application. Unless there's a better way to design it in web2py. On Apr 22, 11:23 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > It depends. If each "part" is supposed to work without the others, > than each part is its own application. > If the parts only make sense together, they belong to one single > application. You can make it more modular using different controllers > for different parts. > > On Apr 22, 8:11 pm, Stodge <sto...@gmail.com> wrote: > > > > > > > > > Quick architecture question. Say I have a project management > > application. Typically I'm used to creating separate django apps for > > tickets and requirements and then I can import modules between them as > > needed. How would this be done with web2py? Is the preferred way to > > create one application that includes both features, or separate > > applications for each, or components? Thanks
