4

1

Hi All,

I love Fogbugz. It's a great tool (It would of course be evan greater with a Windows client but that's another story).

The thing I often get wrong when submitting a case is the project field. I simply forget to fill it in. The problem is, as self-employed developer, I work on an amount of projects for different customers. So I always filter my cases by project. You get it: If a project field is incorrectly filled-in, I won't see that bug until I go work on the other project.

One way I found to workaround this is to create a set of windows shortcuts to file bugs in the correct project. Such as: http:///FogBugz/default.asp?command=new&pg=pgEditBug&ixProject=9

But often, I'm in my list of cases and simply click the 'new case' link. And I inconsciously assume that the bug is for the project currently displayed. But it's not. And boom! I don't realize I filed the bug for another project (the previous one for which a bug was entered?)

I would be grateful for anything you could do to address this problem, whether the solution I suggested or something else.

TIA,

Serge.

Fog Creek Case FC1964974

flag
I agree - the new case button should be context aware and use the content of the current view to prefill fields. If on the list view, the current filter; if on a report (or schedule as they are now called), the selected project, etc. – David Mitchell Oct 24 2010 at 20:45
2 
 Note that if you add a case via the "Add Case" links that show up at the bottom of groups on the case list page, those will use the information from your filter. – Daniel LeCheminant♦ Oct 25 2010 at 11:45

1 Answer

1

Hmmm. The way it operates now is with "sticky" defaults. The project will default to the last project (and area) you entered a case in. This is predicated on the fact that you'll have to change the project less often if we always default to the last thing you added.

We too make lots of use of bookmarks and bookmarklets (which can take information from the current case and add it to the new case). Context-aware implementations are notoriously difficult to do. The net result of making something context-aware, if you cannot make it blatantly apparent the context which obtains, is to confuse the user, which is the last thing we want to do. They either stop using the feature, or stop using the product altogether.

I guess it makes sense if you have a filter on a given project that the New Case link would add to that project (and maybe area). This might be a good time to address the fact that Send Mail allows you to create cases in projects that don't get mail.

We'll file a feature and get back.

link|flag
Rich, that's my point: I don't want it to keep the settings of the previous new case. I'd rather like it to take the setting sof my last selected filter, such as the 'Add case' link pointed to by Daniel in his comment. – Serge - appTranslator Oct 26 2010 at 6:49

Your Answer

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