A forum for technical support discussion related to Fogbugz.
We are getting ready to upgrade to FogBugz 4.0 and I took a chance to look at the screenshots posted on your site. My arch nemisis is still in there. Having the entry for the project and area separated from the rest of the data entry on a case is really annoying. Especially since it defaults to the last value you entered. it is very easy to miss those fields. Using the 3.0 version I have had to add a task to my to-do list for every week to read over the week's bugs and correct any mistakes in these two fields. I find about 2-3 mistakes per week per developer on this particular issue. At the very least force them to pick something and default it to blank.
Hi! Thanks for your feedback.
We won't require any fields to be filled out because we would much rather have people enter bugs without titles and in the wrong project, than not have them enter bugs at all. We've learned that the more required fields you have, the more impediments there are to adding new cases.
Do the developers who forget to set the project and area actually change any of the other values (fixfor/etc)? Since those values are keyed off the project/area settings, which are set off to be more prominent, I suspect they are just typing in a bug real quick and hitting submit. I think they aren't even looking at any of the other fields, so moving project and area wouldn't help this case. It would make project/area less obvious.
But the good thing about this is that they are entering the bugs regardless.. because it is quick and easy. We'd much rather have to manually change the project for a few bugs, than have developers not enter cases because it takes too long (every time you try to submit a case, it yells at you to pick a project, then an area, then it says, 'You forgot a title'!) I realize it must be frustrating to have to fix these cases, but you've got them in the system which is the whole focus of FogBugz.
Actually it is the Area they always forget to change. It defaults to the last value entered and is so far up in the corner (still running 3.x) that the programmers and I often don't notice it until we run a filter that is missing items. I think the best answer is just put all the editable fields for a case next to each other so you don't miss them accidentally.
This topic is archived. No further replies will be accepted.Other recent topics