Project

General

Profile

Actions

User story #2918

closed

Make the Technical logs table from a node view fixed height

Added by Matthieu CERDA over 11 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
4
Assignee:
-
Category:
Web - Nodes & inventories
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 #1

Updated by Jonathan CLARKE over 11 years ago

  • Assignee set to Jean VILVER
Actions #2

Updated by Jonathan CLARKE over 11 years ago

  • Priority changed from 3 to 4
Actions #3

Updated by Jean VILVER over 11 years ago

  • Status changed from New to Pending technical review

Fixes in #2915.

Actions #4

Updated by Nicolas CHARLES over 11 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 #5

Updated by Jonathan CLARKE over 11 years ago

  • Target version changed from 2.4.0~rc1 to 2.4.0~beta5
Actions #6

Updated by Jonathan CLARKE over 11 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 #7

Updated by Jonathan CLARKE over 11 years ago

  • Status changed from 2 to Discussion
Actions #8

Updated by François ARMAND over 11 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 #9

Updated by Jonathan CLARKE over 11 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 #10

Updated by François ARMAND over 11 years ago

  • Target version changed from 61 to 2.4.2
Actions #11

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.2 to 2.4.3
Actions #12

Updated by Matthieu CERDA about 11 years ago

  • Target version changed from 2.4.3 to 2.4.4
Actions #13

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.4 to 2.4.5
Actions #14

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.4.5 to 2.4.6
Actions #15

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.4.6 to 2.4.7
Actions #16

Updated by Nicolas PERRON over 10 years ago

  • Status changed from Discussion to 8
  • Target version changed from 2.4.7 to Ideas (not version specific)
  • % Done changed from 100 to 0
Actions #17

Updated by Benoît PECCATTE almost 9 years ago

  • Status changed from 8 to New
Actions #18

Updated by François ARMAND almost 4 years ago

  • Status changed from New to Resolved

It's the case now.

Actions

Also available in: Atom PDF