Project

General

Profile

Bug #5718

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

Added by Nicolas CHARLES over 4 years ago. Updated about 2 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 ...

Associated revisions

Revision 74fa16d9 (diff)
Added by Nicolas CHARLES about 2 years ago

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

Revision 4afc44bb (diff)
Added by Nicolas CHARLES about 2 years ago

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

History

#1

Updated by Vincent MEMBRÉ over 4 years ago

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

#2

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.4 to 2.11.5
#3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.5 to 2.11.6
#4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.6 to 2.11.7
#5

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.7 to 2.11.8
#6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.8 to 2.11.9
#7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.9 to 2.11.10
#8

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.11.10 to 2.11.11
#9

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.11.11 to 2.11.12
#10

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.11.12 to 2.11.13
#11

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.11.13 to 2.11.14
#12

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.14 to 2.11.15
#13

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.15 to 2.11.16
#14

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.16 to 2.11.17
#15

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.17 to 2.11.18
#16

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.18 to 2.11.19
#17

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.19 to 2.11.20
#18

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.20 to 2.11.21
#19

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.21 to 2.11.22
#20

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.22 to 2.11.23
#21

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.23 to 2.11.24
#22

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.24 to 308
#23

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 308 to 3.1.14
#24

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.14 to 3.1.15
#25

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.15 to 3.1.16
#26

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.16 to 3.1.17
#27

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.17 to 3.1.18
#28

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.18 to 3.1.19
#29

Updated by François ARMAND about 2 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
#30

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.19 to 3.1.20
#31

Updated by Jonathan CLARKE about 2 years ago

  • Assignee deleted (Vincent MEMBRÉ)
#32

Updated by Nicolas CHARLES about 2 years ago

  • Assignee set to Nicolas CHARLES
#33

Updated by Nicolas CHARLES about 2 years ago

  • Status changed from New to In progress
#34

Updated by Nicolas CHARLES about 2 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
#35

Updated by Nicolas CHARLES about 2 years ago

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

Updated by Vincent MEMBRÉ about 2 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.

Also available in: Atom PDF