On Fri, Aug 02, 2013 at 11:06:53AM +0000, Ram Ganesh wrote: > Hi, > > While triaging bugs I noticed that many bugs had affectedVersion > field as empty. This makes it difficult to guess the > version/release the reporter was on while filing the bug. Can we > make the affectedVersion field a mandatory field instead?
Indeed this would be nice to have. But the reason I think we are not seeing it is not knowing what the affectsVersion should be. Bugs are coming from: 1) Users reporting from the field 2) QA filing bugs from jenkins builds 3) Bugs encountered on master faced by those working on code Those in 1) usually add the information to their description. But could use a command line method to extract this information to make reports clearer. Alex made an enhancement to add this to the jar's manifest. But it's still not something that can be extracted easily. Those in 2) don't know if an unreleased -SNAPSHOT version of the build would need to be put in the affectsVersion and if so what the HEAD of the build is. Again a tool would help. Because one who fixes the bug will almost *always* need the commit-sha1, without which reproducing the bug can be tough. and those in 3) don't have any option on JIRA so I've started to set affectsVersion to 'Future' to denote master and add the HEAD of my repo in the description. I notice these can get improperly triaged. -- Prasanna., ------------------------ Powered by BigRock.com
