User story #2918: Make the Technical logs table from a node view fixed height - Rudder - Issue Tracker

Actions

Copy link

User story #2918

closed

Make the Technical logs table from a node view fixed height

Added by Matthieu CERDA about 12 years ago. Updated over 4 years ago.

Status:

Resolved

Priority:

Assignee:

Category:

Web - Nodes & inventories

Target version:

Ideas (not version specific)

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

Make the Technical logs table from a node view fixed height, because currently, when searching for old logs, we have to chase the "next" button as it permanently moves as you click on it. It gets frustrating very quickly.

Actions

Copy link

Updated by Jonathan CLARKE about 12 years ago

Assignee set to Jean VILVER

Actions

Copy link

Updated by Jonathan CLARKE about 12 years ago

Priority changed from 3 to 4

Actions

Copy link

Updated by Jean VILVER about 12 years ago

Status changed from New to Pending technical review

Fixes in #2915.

Actions

Copy link

Updated by Nicolas CHARLES about 12 years ago

Status changed from Pending technical review to 10
% Done changed from 0 to 100

There's nothing to review, so going to functionnal review

Actions

Copy link

Updated by Jonathan CLARKE about 12 years ago

Target version changed from 2.4.0~rc1 to 2.4.0~beta5

Actions

Copy link

Updated by Jonathan CLARKE almost 12 years ago

Status changed from 10 to 2
Assignee deleted (~~Jean VILVER~~)
Target version changed from 2.4.0~beta5 to 2.4.0~rc2

This is not at all functional. The height of the table continues to vary from page to page, causing the "Next" button to move up and down, making it very hard to scroll through pages.

Actions

Copy link

Updated by Jonathan CLARKE almost 12 years ago

Status changed from 2 to Discussion

Actions

Copy link

Updated by François ARMAND almost 12 years ago

(I also check and it does not work).

I propose to re-qualify that as a bug, as now, it should work and does not.
I also propose to change the target version to 2.4.1, as it does not seem to be a blocker for 2.4.0.

Actions

Copy link

Updated by Jonathan CLARKE almost 12 years ago

Target version changed from 2.4.0~rc2 to 61

François ARMAND wrote:

(I also check and it does not work).

I propose to re-qualify that as a bug, as now, it should work and does not.
I also propose to change the target version to 2.4.1, as it does not seem to be a blocker for 2.4.0.

Agreed.

Actions

Copy link

#10