|
While this functionality might be neat power user stuff, wouldn't it be simpler and more user friendly to get the search unions into the main query page as requested in
Everyone here make sure you Vote for JRA-1560. It's now up to 3rd place.
This looks to be a duplicate of JRA-6527. So, Atlassian, if you agree, please resolve one of them and let's all consolidate our votes on just the one issue.
<irony> We'll combine the two issues - making a UNION of sorts </irony> Neal,
I agree. Thank you for tracking this down. Cheers, |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
But since I often open a lot of my own issues myself, I really want to see "Open Issues submitted by me (assigned to any team other than mine)". And I thought I could do that by defining an "Open Issues Assigned to my team" filter and defining another filter that is just ("Open Issues submitted by me" minus "Open Issues Assigned to my team").
If the query engine knew that the "Open Issues" were the same set in both queries, that could be optimized out and either cached or only evalutated once.