[jbosstools-dev] jbds_current_nofixversion filter is... strange

[Max Rydahl Andersen]

Then set the fix version where the decision was made to not fix, reject or where the duplicate was identified. Remember same issue can exist on multiple streams. 

That's how we've done it as long as I remember and it is nice extra context to have if an issue comes back again. 

/max
http://about.me/maxandersen


> On 11 Sep 2015, at 00:16, Rob Stryker <rstryker at redhat.com> wrote:
> 
> Hi:
> 
> I'm not sure where this filter comes from, but its on my dashboard. 
> jbds_current_nofixversion
> 
> Current query is:  filter = jbds_current AND fixversion is EMPTY
> 
> The filter has 6 results, all of which are closed as wont-fix, rejected, 
> or duplicate issue.  So this filter could probably be refined a bit. I 
> would imagine rejected or wont-fix issues don't actually require a 
> fix-version, at least....  I'd also assume that duplicates also don't 
> need a fix version, since the duplicate issue is often closed while the 
> other issue is still open.
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev