Fix Year Crossover Issue in Discover!

[#1]

Ever since its inception, it has not been possible to run a Discover report that crosses over from say November to June of the next year.  Over the years, they have made it so you can see a few months of data (say from Nov until Feb of the next year), but we need the ability to pull any date range in Discover.  Thanks!

[#2]

Here here!  I spend an extra hour working today just because of this limitation

[#3]

Yes! Please fix the year crossover issue. If a fiscal year crosses the calendar year - what a pain to run YTD reports in Discover!

[#4]

Running 4th quarter reports where our quarter is 11/1 - 1/31 takes twice as long as it should. For the price of discover, there should be no limit imposed on year crossover. This should be fixed.

[#5]

This is possible in SiteCatalyst so why not Discover?

[#6]

I've never been able to even make the short view (e.g. Nov-Feb) work.  I still get cut off at the Dec 31 date!

In my experience the hardcore, full-time analyst will use Discover as the chief workhorse.  Actionable intelligence comes from the multi-dimensional analysis that Discover provides, and not the flat, snapshot reporting that SiteCatalyst provides.  Therefore, the kind of enhancement we're asking for is both obvious and crucial.

[#7]

This feature is being considered for an upcoming release of Discover. How important is it that Discover also support SiteCatalyst's custom calendar configurations as part of year crossover ability?

[#8]

My vote would be to not hold up this feature initially for the custom calendar since my hunch is that only a small % of people use that (maybe you can check internally how many Discover customers use that, but I thin it will be small)...

[#9]

Done!