Project: appceleratorstudio
Issue TISTUD-6438: Switch to using Findbugs rank over priority
Findbugs (and the Jenkins plugin) defaults to using "priority" for sorting issues into high/normal/low. The reality is that "priority" was defined as closer to "confidence level" in the way it's used. With Findbugs 2.0 they introduced "rank" which is the notion of how "scary" a bug is. I'd argue that's a better thing for us to track and determine the high/normal/low values and thresholds to use. The plugin doesn't let you change how the mapping is done, so I looked at the source and it appears to be: 1-4: High 5-9: Normal 10+: Low. (Compare this to Findbugs definition: scariest (rank 1-4), scary (rank 5-9), troubling (rank 10-14), and of concern (rank 15-20).)
Story points: 2