Project

General

Profile

Actions
Copy link

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 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Web - UI & UX
Target version:
5.0.18
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
56
Name check:
To do
Fix check:
Checked
Regression:

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
Copy link
 #1

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #2

Updated by François ARMAND about 5 years 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
Copy link
 #3

Updated by Raphael GAUTHIER about 5 years ago

  • Status changed from New to In progress
Actions
Copy link
 #4

Updated by François ARMAND about 5 years 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
Copy link
 #5

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 5 years ago

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

Updated by Alexis Mousset almost 5 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

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

Updated by Raphael GAUTHIER over 4 years ago

  • Priority changed from 59 to 58
Actions
Copy link
 #10

Updated by Raphael GAUTHIER over 4 years 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
Copy link
 #11

Updated by Raphael GAUTHIER over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

  • Priority changed from 58 to 56
  • Fix check changed from To do to Checked
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 4 years 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
Copy link

Also available in: Atom PDF