Project

General

Profile

Bug #16402

Cannot set Compliance reporting mode on "Non compliant only" in settings tab

Added by Elaad FURREEDAN 10 months ago. Updated 9 days ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

When in try to set Compliance reporting mode on "Non compliant only" in the webapp, the "Save changes" button disapear and therefore not allowing us to choose this option and save it.


Files

non_compliant_settings.gif (190 KB) non_compliant_settings.gif Elaad FURREEDAN, 2019-12-12 23:01
#1

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 6.0.1 to 6.0.2
#2

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 6.0.2 to 6.0.3
#3

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 6.0.3 to 6.0.4
#4

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 6.0.4 to 6.0.5
#5

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 6.0.5 to 6.0.6
#6

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 6.0.6 to 6.0.7
#7

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 6.0.7 to 6.0.8
#8

Updated by Raphael GAUTHIER 3 months ago

  • Status changed from New to In progress
  • Assignee set to Raphael GAUTHIER
#9

Updated by Raphael GAUTHIER 3 months ago

The "Save" button is still here but he appears under the "Agent Run Heartbeat" section, which makes it difficult to see. The title of this section should not have the same style than the title of its parents section ("Compliance reporting mode")

#10

Updated by Raphael GAUTHIER 3 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/3118
#11

Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 6.0.8 to 6.0.9
#12

Updated by Raphael GAUTHIER about 2 months ago

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

Updated by Vincent MEMBRÉ 23 days ago

  • Target version changed from 6.0.9 to 6.0.8
#15

Updated by Vincent MEMBRÉ 9 days ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.8 and 6.1.4 which were released today.

Also available in: Atom PDF