Welcome to the FogBugz Knowledge Exchange

Question

8

1

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.

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.

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?

edited May 1 2012 at 16:28

adambox♦♦
23.9k●1●22●63

asked Aug 24 2010 at 21:00

kscott
81●3

Ted · Answer 1 · 2010-08-24 21:54:10Z UTC

1

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.

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.

answered Aug 24 2010 at 21:54

Ted♦♦
5,000●4●10

	We wrote some custom reports to give each business owner views of their 'projects', as well as use some of the other project functionality in FogBugz. Areas don't seem to permeate as many areas of FogBugz as Projects do. But i am looking at how we may be able to switch to this way of thinking without losing anything. thanks. – kscott Aug 25 2010 at 18:47
	That's a good point, too. Projects and areas aren't always interchangeable in other parts of the product. A configuration option for the plugin does seem reasonable. – Ted♦ Aug 25 2010 at 20:13

adambox · Answer 2 · 2012-05-01 16:29:09Z UTC

1

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!

answered May 1 2012 at 16:29

adambox♦♦
23.9k●1●22●63

Isabelle · Answer 3 · 2011-07-21 23:10:23Z UTC

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".

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:

multiple products
one backlog per product
items get pulled from product backlog into product releases (projects/etc.)
items get pulled from product releases into release milestones (sprints/iterations/etc.)

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.

Any advice on how to map this model into the FogBugz model?

Andrei Prislopski · Answer 4 · 2012-10-17 15:54:05Z UTC

0

We need this feature as well.

answered Oct 17 at 15:54

Andrei Prislopski
1●1

Frank · Answer 5 · 2012-10-17 16:29:29Z UTC

0

Adding my yes vote to this feature. Please add it as soon as possible!

answered Oct 17 at 16:29

Frank
1

Feature Request: Global (not project-specific) backlog

5 Answers