Answers will be carefully considered by the FogBugz team.
Note: for usability issues unrelated to UI beauty, see this question:
|
5
2
|
Answers will be carefully considered by the FogBugz team. Note: for usability issues unrelated to UI beauty, see this question: |
|||
|
|
|
15
|
Two words: code view I'm pasting code snippets, SQL statements, dumps, whatever, all day long into Cases and its just unreadable gibberish, tedious to work through. Attach snippets did not really work. At the bottom it probably comes down to being able to use some kind of markup |
||||||||||||||||
|
|
13
|
It would be nice if the search box was much wider. I use several saved filters that were made by taking advantage of the advanced search queries, and sometimes I just want to change one or two of the variables. It can take a lot of scrolling through the current search box if the variable I want to change is in the middle of my query. I know a work around would be to save that filter as well, but I already have several and try to keep my list as short as possible. |
|||||||||||
|
|
11
|
Something that instantly struck me when I started using FogBugz is the way subcases are indented in the list. From a quick glance it looks like the parent case is a subcase of the previous case in the list as it has an arrow in front of it. I've made an image to display it easier. (A) is how it looks today, (B) is how I'd like it to be. In the example below (A) it looks like case 48 is a subcase of 46.
|
||||||||||||||
|
|
9
|
I'd vote for fixing up the filter customizer. On my screen, it scrolls off the bottom, making it difficult to navigate. But it appears there is enough screen width you could make two columns out of that information. (But not much is wrong anymore. I find 7.x much better looking than 6.x. Beyond the new features, its the little things like rounding the corners, picking colors that are a little bit softer, slightly better fonts, better shadowing... it's all very subtle... much more pleasant.) |
|||
|
|
8
|
We think that the Fogbugz should be better use wide screen displays. Why only use a fixed width? Using a bugmonkey script we have applied CSS and some JS in order to
Screenshots before&after is here: http://img12.imageshack.us/img12/7561/fogbugz.png Our bugmonkey script is here: http://fogbugz.stackexchange.com/questions/59/bugmonkey-scripts-post-them-here/116#116 |
||||||||||
|
|
5
|
"Also sent" is maybe a little uselessWith some customers we correspond a lot and have a lot of cases, so having "Also sent" under Correspondent for each case is a little useless to us, because there are so many cases to choose between. They only take om valuable screen estate. Is this usability or aestetics? Or both? Overall I'm pretty satisfied with the aesthetics. Maybe the blue color could be toned a little bit more towards the color scheme from stackexchange, which I find a little more "serious". You could also drop the shadows effect on the case history for a case. Tighten it all up a bit. Use larger fonts in headings and menus. Some of you probably already thought of this, but here is someone else from the outside also saying it :-). |
|||
|
|
2
|
All of the emails that I receive from fogbugz have "^M" characters at the end of the lines. I read the emails using Mutt on a linux box, so I'm not too surprised about line-ending problems. But, fogbugz is the only sender whose emails don't look right. I get emails from outlook, other websites, cronjobs, and all kinds of places that don't have ^M at the end. Fogbugz is the sole exception. |
||||||||
|
|
2
|
The export to csv option is hard to find. We use this feature a lot but I always have questions from my team about where to find it. I also forget where it is after a short vacation or such. |
|||
|
|
2
|
The Admin Dashboard isn't the nicest looking UI element. I don't care for those dashed lines. Change those to solid lines and put some drop shadows on those boxes like you have on the case editing form. That would be prettier.
|
||
|
|
|
1
|
I don't know if this is to be considered "ugly", but it is to me. I have recently started using subcases, instead of closing cases as duplicate (when a customer inadvertently opens a new case with a new email). Using subcases for this purpose are easier for me, because sometimes their emails include screenshots, etc. However, each time I refresh my screen, my collapsed subcases are once again expanded. I don't want to look at a list of perhaps 25 cases, when I really only have 15 active cases. I just discovered that if I close the subcases, they will stay collapsed when I refresh my screen. This is okay, but not ideal. Maybe it's different for other people, but I would rather see a collapsed list as a default, rather than have to collapse my list several times a day. I know it's mostly just a psychological downer when my list is long. It makes me panic when it gets too long! |
||||||||
|
|
1
|
Print style For me, the print style (specifically for the case list) could be a bit nicer. Right now I use a Stylish script for printing.
|
||
|
|
|
1
|
It would be nice if we could completely customise the appearance of a wiki - Ideally it would be great if I could drop the fogbugz header / navigation bar and replace it with out own branding. This way I could seamlessly integrate the fogbugz wiki into our existing website and use it for online help. |
||||||
|
|
1
|
I would really like resolved cases to have a strikethrough css style (ala bugzilla). This allows for immediate recognition of open and closed cases. At the moment you must mouse over (not available when Javascript is turned off) a case to see it's resolved status. |
|||
|
|
1
|
When adding a subcase on the case list screen, the check (OK) and X (cancel) icons don't have a transparent background, so you see an ugly white frame around them. |
||
|
|
|
1
|
I would LOVE to see you guys hire a top designer; you know the cream of the crop in the web design community, and overhaul FogBugz' look and feel. FogBugz is very plain, even though it's a great product. Check out Sifter, GetDoneDone, and others. FogBugz suffers from looking like it's designed for the early 2000's. Joel himself should know that people place unconscious trust in products that present well. If FogBugz looked better, you'd probably get more sales. |
||||||
|
|
1
|
The first time, when I used the wiki I havn't found the save button. It would be a great idea to add the text "save" nearby the disk icon. |
||
|
|