Issue trending report

I don't think so. You can definitely create an issues report. But as soon as you want a set of months on the X-axis, you are going to have to specify what these months mean. For example, I can create an issues report and specify that I want the X-axis to be months denoting the month that the issue was created. Then I can have a chart that shows me the issues opened that month. Or I can create an issues report and specify that I want the X-axis to be months denoting the month that the issue was closed. Then I can have a chart that shows me the issues closed that month. But I can't do both. The X-axis cannot be months denoting the month that the issue was opened AND closed (unless you're specifically looking for issues that were closed in the same month that they were opened which is generally not a useful statistic). -skye

Hi John, I concur with Skye. To reassert her X-axis comment slightly differently: on any given chart, each item (an Issue, in this case) can appear (as a row) and "count" (e.g. in a bar chart) only once , where what you'd like to do is have each Issue appear and count twice, based on the month it was opened and the month it was closed (...or is not closed yet). So, the simple workaround is to create two charts -- one grouped by Entry Date (month), the other by Actual Completion (month) -- and show them "stacked" one above the other on a single dashboard, so the user can correlate them (relatively) easily. The wait:what? alternative is to use a calculated parameter that watches for the Entry Date (which is of course, upon initiation) and the first (yeah, it happens) Actual Date and in each case, tag a special value (e.g. "~ISSUE_CREATED~" and "~ISSUE_CLOSED~") that will be captured as two separate NOTES behind the Issue. Since the NOTES object is 1:many to the Issue, you can then create a single NOTES report that filters for those two special tags, groups them by their independent Entry Date (i.e. "one X-axis"), and then in a list view, use Smart Reporting to highlight the _CREATED differently from the _CLOSED items since (alas) you won't be able to chart them, since Notes do not support Custom Data. Regards, Doug Doug Den Hoed - AtAppStore

thanks Doug, I had a feeling there was a clever way to do it, but I am a bear of little brain where calculated params are concerned. Glad you stepped in :) -skye

Thanks gents.