4

1

Possible Duplicate:
Feature Request - Solution for too many projects

After some searching, seems no one has asked this; if this is redundant, I'm sure I will receive the appropriate hand-slap...

The problem: We have a number of projects, some large and some small. Our project list has grown and its become difficult to manage. Besides that, its just plain ugly. (I'm using a wiki to help out now, but 2 documents for one task = issues ) After a while I forget (imagine that) some project details and have to consult "other" document sources.

Over the past year, we have standardized on using FogBugz more for our requirements and work tracking (love the new expanded work items and nested cases). Now, if we can capture more "project" level detail inside FogBugz, we could eliminate another document... (a good thing)

I would like to request 2 added fields for projects:

  1. Category or TAG Field
  2. Notes Field

The Category (or TAG) would filter displayed projects. I would prefer to either select the category before seeing the list of projects, or provide a check box, or TAG field, to show the projects with which I am interested. Creating a [deleted] or [closed] tag, for example, would resolve a previous user's feature request, helping to keep closed projects silently tucked away. The ability to have multiple TAG's per project would be way kewl...

The Notes field could be a simple text field (lots of text space desired), or perhaps even a wiki style text field where I can describe this project -- This field would enable me to record WHY and for WHOM this project is being generated, as well as any other pertinent project details.

I believe these fields are in line with the spirit of FogBugz -- clean and simple operation. The world has embraced Stack Overflow and know how tags work to filter content so the learning curve is also reduced. A push in our shop is also to reduce the number of documents we produce to generate a product -- this will be a GREAT help towards that end.

Fog Creek Case FC2049313

flag
1 
see also: fogbugz.stackexchange.com/questions/1385/… – Greg Saven Mar 3 2010 at 1:05

2 Answers

1

A project description field could be nice as long as it's not too long. This could also display next to the project name in the reports/charts - which would be nice.

I think the project "tag" thing fits with the star functionality that already exists at the case level. It sounds like your hitting up against a wall that I'm noticing, too. FB is great for looking at what's going on at the project level, but the ability to look at multiple projects (a la program/portfolio management) would be really nice.

link|flag
0

  1. What version of FogBugz are you using?

  2. How many groups of people are involved?

  3. How does your workflow operate currently within FogBugz (including what you mean by your projects)?


For the project items, going without detail of your situation, are these independent projects? Are they suited to areas within a FB project? Entire FB rojects can currently be deleted, and all cases associated with those projects are still searchable (but the project won't show in the drop-down for new cases, etc.). Having tags for projects (as opposed to just cases) seems like confusion to me.


For a notes field, for a whole FB project? Seems like having an overview like that would be better in the wiki. As for cases, while not providing for markup (some work is being done http://fogbugzcasemarkdown.codeplex.com/), the Custom Fields plugin with Version 7 may be desired. A "long text" field placed at the top provides quite a bit of room right at the top.

link|flag
Were using version 7 of FogBugz. Currently only developers and QA have licenses -- I am, however, adding licenses today for Support Services. – Borzio May 19 2010 at 15:11
1 
Keeping details of projects with projects keeps the information together–having a separate wiki means navigating away from the project. Naming a wiki with @@projectname, for example, may be an easy way for the FogBugz to “know” that this wiki doesn’t display on the global wiki page and does display alongside the projects, for example. Additionally, clicking on a little icon to the right (or left) of the project name can launch the wiki – the key item is free text to describe the project easily accessible. – Borzio May 19 2010 at 15:11

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.