Greetings, hackers,
I've just completed a little Jira house-cleaning which should result in better understanding of project status and better sensor data analysis.
There are now two public filters:
* 6.5 Remaining Issues * Unscheduled Issues
Which correspond to the current 'working set' of unresolved issues and the not-yet-scheduled unresolved issues. As part of getting this together, I had to open about a dozen closed issues and assign them a fix version, so sorry for all the Jira emails that some of you have received just now.
What I also did was to do a bulk change of the Unscheduled Issues to make all of them 'minor'. In terms of the Issue telemetry, that makes it relatively simple to track the 'important' issues by simply filtering out all of the issues that have priority 'minor' or 'trivial'.
As we move forward, what we should do is as we elevate an issue from 'unscheduled' to having an actual release number associated with it, we elevate the priority above 'minor', and now it will show up in the telemetry streams.
There are, of course, a bunch of different ways we could accomplish this filtering in terms of the telemetry stream, all with different trade-offs. For example, we could extend the sensor data representation and analyses to support a 'release number'. That simplifies our analyses, but adds a new representational constraint. Anyway, let's try this out for a while and see what happens.
Cheers, Philip
