Project

General

Profile

Actions

Bug #15557

closed

When adding tags, if anything is wrong in the directive form, all unsaved tags are wiped out

Added by Félix DALLIDET over 1 year ago. Updated 10 months ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
56

Description

To reproduce on a 5.0:

Create a directive, add tags, but let a mandatory fields of the directive parameters empty, click save and it should wipe your tags.
This is very annoying.

Another bug is:
if you add one tag, click the "+"
your entry should still be fulfilled in the tag form, then change the key tag and keep the same tag value, save, it wipes all your unsaved tags.

Actions #1

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.13 to 5.0.14
Actions #2

Updated by François ARMAND over 1 year ago

  • Assignee set to Raphael GAUTHIER
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Effort required set to Very Small
  • Priority changed from 0 to 79

This is extremelly disturbing even if not grave - the kind of bug that make the user mad.

Actions #3

Updated by Raphael GAUTHIER over 1 year ago

  • Status changed from New to In progress
Actions #4

Updated by François ARMAND over 1 year ago

  • Effort required changed from Very Small to Small
  • Priority changed from 79 to 66

It's at least "small" and not very small, because tags are an angular app and not in the form. So when the form is reloaded, the angular app is reseted, and tags discarded. Correction is not obvious.

Actions #5

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.14 to 5.0.15
Actions #6

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 66 to 64
Actions #7

Updated by Alexis MOUSSET about 1 year ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 64 to 61
Actions #8

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 5.0.17 to 5.0.18
  • Priority changed from 61 to 59
Actions #9

Updated by Raphael GAUTHIER 12 months ago

  • Priority changed from 59 to 58
Actions #10

Updated by Raphael GAUTHIER 12 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/3006
Actions #11

Updated by Raphael GAUTHIER 12 months ago

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

Updated by Vincent MEMBRÉ 10 months ago

  • Priority changed from 58 to 56
Actions #13

Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.18 and 6.1.2 which were released today.

Actions

Also available in: Atom PDF