most recent 30 from http://fogbugz.stackexchange.com 2013-05-20T03:20:57Z http://fogbugz.stackexchange.com/feeds/question/4155 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/4155/feature-request-global-not-project-specific-backlog kscott 2010-08-24T21:00:56Z 2012-10-17T16:29:29Z

<p>We are an internal corporate shop supporting dozens of internal only applications, where every part of the business wants whizzbang features added to their part of the internal world all the time.</p> <p>We use a modified Scrum system where our sprints are made up of backlog items from across the spectrum of apps. "This sprint the billing app will get a new processing module, the reporting app will have these 3 reports written, and the public websites will have the search module rewritten to use Ajax" etc.</p> <p>So we use only global milestones (each sprint) and also want to use a global backlog ordering (so the business owners can all sit it a room and argue with each other about which feature gets implemented first in our next sprint), but it seems there is only project specific backlogs. Is there a way to use the backlog globally?</p>

http://fogbugz.stackexchange.com/questions/4155/feature-request-global-not-project-specific-backlog/4156#4156 Ted 2010-08-24T21:54:10Z 2010-08-24T21:54:10Z

<p>My best suggestion is that you should arrange everything to be in one project and use areas to divide it up into billing/reporting/... and so forth.</p> <p>I think of projects as teams. If a team works on more than one project, it's really just a big project with multiple areas.</p>

http://fogbugz.stackexchange.com/questions/4155/feature-request-global-not-project-specific-backlog/8850#8850 Isabelle 2011-07-21T23:10:23Z 2011-07-21T23:10:23Z

<p>I had a similar question stemming from our usage pattern with other tools. We create multiple products, and of course each product has a new release every so often. Traditionally, I would think of each release of each product as a "project".</p> <p>Currently, we're looking at whether it is viable to switch to FogBugz, but I'm having trouble figuring out how to model the following in FogBugz:</p> <ul> <li>multiple products</li> <li>one backlog per product</li> <li>items get pulled from product backlog into product releases (projects/etc.)</li> <li>items get pulled from product releases into release milestones (sprints/iterations/etc.)</li> </ul> <p>This is very similar to the OP's issue, in that we would like to have a backlog tracked above the project level, but slightly more complex in that we also would like to have one such backlog per product.</p> <p>Any advice on how to map this model into the FogBugz model?</p>

http://fogbugz.stackexchange.com/questions/4155/feature-request-global-not-project-specific-backlog/10344#10344 adambox 2012-05-01T16:29:09Z 2012-05-01T16:29:09Z

<p>Thanks for the feature request! We'll file it as an official request when it reaches our top 100 feature requests by votes. To get it there, vote up this question!</p>

http://fogbugz.stackexchange.com/questions/4155/feature-request-global-not-project-specific-backlog/10881#10881 Andrei Prislopski 2012-10-17T15:54:05Z 2012-10-17T15:54:05Z

<p>We need this feature as well.</p>

http://fogbugz.stackexchange.com/questions/4155/feature-request-global-not-project-specific-backlog/10882#10882 Frank 2012-10-17T16:29:29Z 2012-10-17T16:29:29Z

<p>Adding my yes vote to this feature. Please add it as soon as possible!</p>