close fullscreen

Ticket

make append work with found_by+status
open
help edit space_dashboard
make append work with found_by+priority
low
help edit space_dashboard
make append work with found_by+tag
CQL
help edit space_dashboard
make append work with found_by+commit
 

make append work with found_by+issues

help edit space_dashboard

Right now if found_by operates on a Search card that uses append/prepend, what you get is the unappended/-prepended cards.

 

make append work with found_by+solution

help edit space_dashboard

We didn't implement this straight away because of performance issues.  Right now found_by merges wql - it doesn't do the inner call separately.

 

The best approach is probalby to make an exception for a/p, such that it performs the search separately when and only when the referenced query has a or p.

 

People doing this will typically want to preserve arrangements in found_by.

 

make append work with found_by+example

help edit space_dashboard

http://test.dwagn.org/wagn/found_by_dropping_append_and_losing_arrangement

 

help edit space_dashboard

If the "arrangement" tokens (sort, dir, limit, offset) are the key issues here, then we may be able to come up with a relatively straightforward limited solution.  The difficulty comes in adding new relationships and operators that are supposed to take effect after the append/prepend, which would mean we have to do a query, monkey with the results, and then do another query or queries.   That's probably a ways out.

 

But if we're just talking about arrangment stuff that can really happen in the initial query (limits, sorting by most things other than content, etc) then we might be able to put this together fairly quickly.  The issue will be making WQL smart enough to know its limits and fail on queries it can't handle correctly.

 

make append work with found_by+discussed in support tickets

help edit space_dashboard