Project

General

Profile

Actions

Bug #5718

closed

In reports list, if the directive contains < >, then the part in < > doesn't appear in the reports

Added by Nicolas CHARLES over 6 years ago. Updated almost 4 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
36

Description

Since Rudder 2.11, if a directive contains < > in its name, this part doesn't appear in the Directive list of reports.
This is quite unfortunate, as Cloning adds < > in the name of directive ...

Actions #1

Updated by Vincent MEMBRÉ over 6 years ago

I think it's not correctly handled by datatable and filtered ...

Actions #2

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.11.4 to 2.11.5
Actions #3

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.11.5 to 2.11.6
Actions #4

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.11.6 to 2.11.7
Actions #5

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.11.7 to 2.11.8
Actions #6

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.11.8 to 2.11.9
Actions #7

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.11.9 to 2.11.10
Actions #8

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.11.10 to 2.11.11
Actions #9

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.11.11 to 2.11.12
Actions #10

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.11.12 to 2.11.13
Actions #11

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.11.13 to 2.11.14
Actions #12

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.11.14 to 2.11.15
Actions #13

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.11.15 to 2.11.16
Actions #14

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.11.16 to 2.11.17
Actions #15

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.11.17 to 2.11.18
Actions #16

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #17

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #18

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #19

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #20

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #21

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #22

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.24 to 308
Actions #23

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 308 to 3.1.14
Actions #24

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #25

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #26

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #27

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #28

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #29

Updated by François ARMAND about 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques
  • Effort required set to Small
  • Priority set to 36
Actions #30

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #31

Updated by Jonathan CLARKE about 4 years ago

  • Assignee deleted (Vincent MEMBRÉ)
Actions #32

Updated by Nicolas CHARLES about 4 years ago

  • Assignee set to Nicolas CHARLES
Actions #33

Updated by Nicolas CHARLES about 4 years ago

  • Status changed from New to In progress
Actions #34

Updated by Nicolas CHARLES about 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1641
Actions #35

Updated by Nicolas CHARLES about 4 years ago

  • Status changed from Pending technical review to Pending release
Actions #36

Updated by Vincent MEMBRÉ almost 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.20, 4.0.5 and 4.1.2 which were released today.

Actions

Also available in: Atom PDF