You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The performance on this page is now better for us :), but we discovered a bug when we load the page with filters.
When we have filters, data is not correcly filtered. We need to refresh the datatable in second time to reload the filtered data.
To reproduce, go on a testcase execution, and click on Execution List (same env and country).
Two calls are launched when we load the page:
The first call in green is correcly done and fill the datatable with the correct filter => this part is OK
But, the other call in red that is done retrieve the complete list of executions (like we open the Execution List without filter) and filled again the datatable with all executions list, so we lost the executions which had been filtered. We think that this call shoudln't be executed.
A solution is to click on the button refresh of the datatable when the call in red is finished, and the correct filtered data is displayed again.
Could you have a look please?
Thank you!
The text was updated successfully, but these errors were encountered:
Hello, this is a known issue that we did not manage to correct yet.
Datatable does not allow to configure filter when init the table. Maybe that there is a way that exeist but we could not find it so far.
Hello,
The performance on this page is now better for us :), but we discovered a bug when we load the page with filters.
When we have filters, data is not correcly filtered. We need to refresh the datatable in second time to reload the filtered data.
To reproduce, go on a testcase execution, and click on Execution List (same env and country).
Two calls are launched when we load the page:
The first call in green is correcly done and fill the datatable with the correct filter => this part is OK
But, the other call in red that is done retrieve the complete list of executions (like we open the Execution List without filter) and filled again the datatable with all executions list, so we lost the executions which had been filtered. We think that this call shoudln't be executed.
A solution is to click on the button refresh of the datatable when the call in red is finished, and the correct filtered data is displayed again.
Could you have a look please?
Thank you!
The text was updated successfully, but these errors were encountered: