Project

General

Profile

action #36307

Remove limit option in Next & previous results tab UI

Added by mitiao about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2018-05-17
Due date:
% Done:

0%

Estimated time:
Difficulty:
Duration:

Description

Remove limit option in UI and set default to 100 next + 400 prev
See commnets in https://github.com/os-autoinst/openQA/pull/1614


Related issues

Related to openQA Project - action #13920: Showing context builds test result in the view of current "Previous Results" Resolved2016-09-27

History

#1 Updated by mitiao about 2 years ago

  • Related to action #13920: Showing context builds test result in the view of current "Previous Results" added

#2 Updated by mkittler about 2 years ago

Ok, a few things which still needs enhancement in my opinion:

  1. When using the route /tests/latest you get a DataTable error. To reproduce, just start your web UI locally and open http://localhost:9526/tests/latest#next_previous.
  2. It would be nice if the query parameter for the limit is updated as before. For that purpose I've once written the helper functions parseQueryParams() and updateQueryParams(params) in openqa.js.
  3. Reintroduce the link to the still valid URL for the latest job in general.

#3 Updated by mitiao about 2 years ago

  • Status changed from New to In Progress

Submitted PR https://github.com/os-autoinst/openQA/pull/1656
to fix DataTable error under /tests/latest and reintroduce the latest scenario URL

limit option will be in next PR

#4 Updated by okurz about 2 years ago

mkittler wrote:

  • Maybe reintroduce the URL for the latest job in general (if okurz needs it).

That's weird wording. Think 1k bug reports on bugzilla.opensuse.org reference that link that is commonly used to find out if the latest one still fails. If this URL is now suddenly invalid it could cause quite some confusion and frustration.

#5 Updated by mkittler about 2 years ago

PR is merged. I can confirm that the link is back and the error gone. So only the 2nd point missing.

okurz Yes, the wording was wrong. The URL was never invalid, only the link has been removed.

#7 Updated by szarate about 2 years ago

  • Target version set to Current Sprint

#8 Updated by coolo about 2 years ago

  • Status changed from In Progress to Resolved

merged

#9 Updated by szarate about 2 years ago

  • Target version changed from Current Sprint to Done

Also available in: Atom PDF