Question

Questions related to Filter Charts in the FogBugz 8.0 Beta:

• I am looking to create charts that look at all projects or a specific project and graph the number of opened or closed cases per day in the project(s). So, I want the X Axis to be dates and I want Y Axis to be number of cases per day. No matter what I do, the Y Axis always seems to be the total number of cases rather than cases per day. What am I missing? Should I be using Column or Line, or is it up to me? Do I need to be sorting by something I am just missing?

• Am I correct that when charting opened and closed cases that each case will show up when it was last opened or last closed rather than every time it has been opened or closed?

• Is it possible to chart incoming email messages or outgoing email messages per project or across all projects? If not, I would really appreciate the Fog Creek team considering it. It's a metric that would prove immensely useful to us.

Love the beta! Many thanks!

Marc :-)

Answer 1

• Charting "cases opened per day" is not currently supported, although it sounds like a good idea. The way you are describing it, it seems like the best way to achieve it would adding a "Date Opened" breakdown.

• Time-based charts of cases that are opened or closed should actually show every time the case has been opened or closed (i.e. it will reflect the actual opened or closed state of the case at the time represented by each point on the graph)

• Charting incoming or outgoing email messages is not currently supported, although we're always looking for ways to make charting/reporting more useful to people and will certainly look at what it would take to add that feature.

It's worth noting that anyone will be able to create custom breakdowns and metrics via an API, so even if Fog Creek doesn't add some of these features, other developers may be able to.

Answer 2

I'm using FogBugz 8.1.4, upgraded from 7.x Great with the charts! The first I looked for was a "per day"(or to prefer per week/month)-chart. So I agree with the above writers. I want to see how number of incoming (or opened or closed..) varies over time. Is number of cases increasing?, when did they start to increase?, what areas are increasing?, did they decrease after our actions in october?.. and so on. The line chart is now showing only the total number of cases, and that makes the above questions difficult for chart to awnser. (to see the slope of the line) Per week/month would be prefered to per day, because it would give a smoothening effect, per day can vary a lot. I think a feature like this would be valuable and appreciated.

thanks, Anders Karlsson

Answer 3

Any news on this?

I'm surprised at this omission in the reporting feature. For me, the first thing I wanted to check with charts after I learned about the feature was "okay, how is my cases closed per day trending?" I need to show my boss that I'm doing more and more each day, right?

So another vote for "Date Opened" and "Date Closed", please! Thanks for considering.

Answer 4

Hi, any news on this? The Fogbugz charting looks great, but sadly we currently have almost no use of it. What we want to do with statistic is to follow/analyse cahnges in number of incoming issues over time. (e.g which areas are increasing/decreasing over time / where do we need to put effort). Per day/week/month breakdown would be appriciated, to detect a trendchange of overall issues or in specific area.

regards, Anders Karlsson

Answer 5

"Date Opened" breakdown would be great!

Answer 6

For some filters, the Number of Cases is monotonically increasing by definition. E.g. when listing all cases regardless of time-dependent state like Status. Then it would be nice to have a differential chart, instead of (or in addition to) the current cumulative chart.

On the opposite, I cannot filter charts on axes that are time-dependent by definition. For example for All cases opened today, I get this message:

Unsupported refinements are not reflected in this chart

Historical charts cannot be generated for filters that use the following unsupported refinements:

Opened In Last

Maybe this can be made to "just work"?