Project

General

Profile

Actions
Copy link

Architecture #10637

closed

Change message must be configurable for policy mode/property change

Added by François ARMAND about 7 years ago. Updated about 2 years ago.

Status:
Backlog
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
6.1.19
Pull Request:
Effort required:
Medium
Name check:
Fix check:
Regression:

Description

In the ticket #10578, we corrected the fact that is was impossible the add/remove property or change policy mode when the change request message was mandatory by setting a default message for such changes. This doesn't let the possibility to the user to explain why he did the change, and so deflect the interest of having a change message (like having a commit message for a source code modification stating "source modified").

We need to let the user be able to input the message in all cases, and making it UX friendly for properties.

It may be an rather big change, so certainly need to be validated (both the target version and what UX we want to use). It seems that 4.1 is a better target for that than 4.0, even if policy mode is a 4.0 thing (we can live with only default message for it, I believe).

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #10578: Cannot add node property when audit message is mandatoryReleasedNicolas CHARLESActions
Actions
Copy link
 #1

Updated by Jonathan CLARKE almost 7 years ago

  • Assignee deleted (Raphael GAUTHIER)
Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 7 years ago

  • Priority changed from 0 to 36
Actions
Copy link
 #3

Updated by Jonathan CLARKE almost 7 years ago

  • Effort required set to Medium
  • Priority changed from 36 to 35
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.2 to 4.1.3
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.3 to 4.1.4
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.4 to 4.1.5
  • Priority changed from 35 to 34
Actions
Copy link
 #7

Updated by Alexis Mousset almost 7 years ago

  • Target version changed from 4.1.5 to 4.1.6
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.6 to 4.1.7
  • Priority changed from 34 to 33
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.7 to 4.1.8
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.8 to 4.1.9
  • Priority changed from 33 to 32
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.9 to 4.1.10
  • Priority changed from 32 to 31
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 31 to 30
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 30 to 29
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions
Copy link
 #16

Updated by Benoît PECCATTE over 5 years ago

  • Target version changed from 4.1.14 to 4.1.15
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 29 to 0
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions
Copy link
 #21

Updated by Alexis Mousset about 5 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions
Copy link
 #22

Updated by François ARMAND about 5 years ago

  • Target version changed from 4.1.20 to 4.1.21
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.1.21 to 4.1.22
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 4.1.22 to 4.1.23
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 4.1.23 to 4.1.24
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 4.1.24 to 588
Actions
Copy link
 #27

Updated by François ARMAND almost 5 years ago

  • Target version changed from 588 to 5.0.13
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #31

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions
Copy link
 #35

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions
Copy link
 #36

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 797 to 6.1.14
Actions
Copy link
 #37

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #38

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #39

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #40

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #41

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #42

Updated by François ARMAND about 2 years ago

  • Tracker changed from Bug to User story
  • Subject changed from Explanation message is not configurable for policy mode/property change to Explanation message must be configurable for policy mode/property change
  • Parent task deleted (#10578)
  • Severity deleted (Major - prevents use of part of Rudder | no simple workaround)
  • Priority deleted (0)
Actions
Copy link
 #43

Updated by François ARMAND about 2 years ago

  • Related to Bug #10578: Cannot add node property when audit message is mandatory added
Actions
Copy link
 #44

Updated by François ARMAND about 2 years ago

  • Description updated (diff)
Actions
Copy link
 #45

Updated by François ARMAND about 2 years ago

  • Subject changed from Explanation message must be configurable for policy mode/property change to Change message must be configurable for policy mode/property change
Actions
Copy link
 #46

Updated by François ARMAND about 2 years ago

  • Tracker changed from User story to Architecture
  • Status changed from New to Backlog
  • User visibility deleted (Operational - other Techniques | Technique editor | Rudder settings)

Move to architecture backlog.

Actions
Copy link

Also available in: Atom PDF