Greetings, The primary reason I spent some time updating this field was to allow searching for bugs. When I use an open source project and something does not work, I generally take a look at the outstanding bugs in a project. If this is not set it can take an inordinate amount of time to wade through all the issues.
A suggestion might be to leave the field blank and make it required in the JIRA setup. This would force people to pick an suitable value. Just a suggestion though. Happy holidays to everyone. Rick -----Original Message----- From: larry mccay [mailto:lmc...@apache.org] Sent: Friday, December 22, 2017 7:27 AM To: dev@knox.apache.org; Kellogg, Richard M. (CIV) <richard.m.kell...@usdoj.gov> Subject: [DISCUSS] Proper Use of JIRA Type Field All - As you may have seen, Rick Kellogg spent what seems like a good amount of time yesterday cleaning up and setting the Type field in the JIRAs to appropriate values. If we feel that this is a worthwhile task then we should probably try and set it to a meaningful value as they come in - as to not allow that to get out of control again. I have certainly been neglectful of this field and only pay attention to the type of a patch when it comes to updating the CHANGES file for a release. @Rick - would you like to describe your motivation for doing all that cleanup (which was much appreciated, btwenera)? thanks, --larry
