Open Stack

Hi, guys,

I found this bug[1] this morning which was fixed just now, and I have
to say, it is my intention that to make the query executions result in
descending order when I implemented the query pagination blueprint,
which is different with workflows list result behavior. Because in
user's perspective, I think it's more convinient to show the lasted
execution first, right? maybe the most commonly used scenario of
'execution-list' is, user creates some executions first, then he/she
just wants to see what's the status of them, it‘s inconvenience for
the users to scroll down the page to find their executions in
ascending order, executions are more time sensitive than workflows.

[1]: https://bugs.launchpad.net/mistral/+bug/1510417

-- 
Regards!
-----------------------------------
Lingxian Kong