On 17 June 2013 17:54, <[email protected]> wrote: > Thanks, Joachim, > > In our business we make products. We also use these products, combined > with third party products, to build a projects for different customers. > Each project is a custom build. > > Will have to think about how to map that into Bloodhound. >
Just a suggestion: You could use keywords in place of Projects. Just by adding a keyword to each relevant ticket you could keep track of what's needed for a Project to be completed. Using custom queries you should be able to get good reporting on the status of projects easily using tags. Alternatively you could change the label of Products to Projects, because that seem to be the major units you're working on. Instructions for how to do that at are at the bottom of my last email. You can then use Components to keep track of the individual products you're building/using. Hope that helps, Joe > > Christopher Murphy, Vice President > Jervis B. Webb Company, 34375 W. Twelve Mile Road, Farmington Hills, MI > 48331 > 248.521.8704 > > DAIFUKU WEBB > Always an Edge Ahead > > > -----Original Message----- > From: Joachim Dreimann [mailto:[email protected]] > Sent: Monday, June 17, 2013 12:47 PM > To: [email protected] > Subject: Re: Creating a new project > > On 17 June 2013 17:08, David Galligani <[email protected]> wrote: > > > On 06/17/2013 06:02 PM, [email protected] wrote: > > > >> Thanks, David. > >> > >> So Products is the same as Projects? > >> > > I can't say ... > > I don't know what you mean for Project :) But I think that's what you > > want . > > > > Yes, we decided to call them Products some time back. They're the same > thing currently as Projects were in Trac, with the major difference to Trac > being of course that you can have more than one (read: many) of them. > > "Product" better reflects how many organisations develop software: They > sell it (or give it away) as products, or they use it internally as > products to do jobs. They are reasonably permanent and many iterations, > versions, milestones, and projects may improve a product over time. > > A project is something you do to achieve an aim, like create introduce a > major change to a product or create a product in the first place. Or take > on a project for a client if you're in a consultancy. By definition they > are more transient. We may re-introduce projects in the future for those > purposes. > > I hope that helps to explain some of the reasoning behind our decision. > You can change the label to project if you prefer in the TracIni file: > https://issues.apache.org/bloodhound/wiki/TracIni > > wiki.label = Wiki > tickets.label = Tickets > products.label = Products > > Cheers, > Joe > > > > > > > > I'm a simple user and quite a noob here , but if I'm wrong I think > > some of the devs will correct me . > > > > Hope it helps > > > > D, > > > > > > > -- > Joachim Dreimann | *User Experience Manager* > > WANdisco // *Non-Stop Data* > > e. [email protected] > twitter @jdreimann <https://twitter.com/jdreimann> > PRIVACY NOTICE: The information contained in this e-mail, including any > attachments, is confidential and intended only for the named recipient(s). > Unauthorized use, disclosure, forwarding, or copying is strictly prohibited > and may be unlawful. If you are not the intended recipient, please delete > the e-mail and any attachments and notify us immediately by return e-mail. > -- Joachim Dreimann | *User Experience Manager* WANdisco // *Non-Stop Data* e. [email protected] twitter @jdreimann <https://twitter.com/jdreimann>
