Issue Counting Formula 9 Jan 2015

Yesterday I fetched issue data from GitHub. Today I extended this with a formula a coworker came up as he said that tickets aren’t the same. You need to rate critical tickets higher, than little glitches that occur nearly never. So he proposed to rate critical tickets with 100, normal bugs with 10 and all other tickets with 1.

So I adjusted the script and also add the ability to create that ranking for sub components that are part of the same bug tracker.

In each graph you clearly see the period after a release with a higher amount of incoming tickets and then some time later a bug fixing period.

This is how the overall ranking graph looks like:


We have separate labels for the core apps, so I calculated their ranking and it looks like this:

apps ranking