Project

General

Profile

Actions
Copy link

Bug #4093

closed

With Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message

Added by Nicolas PERRON about 11 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
5 (lowest)
Assignee:
-
Category:
Web - Config management
Target version:
3.1.19
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

On Rudder 2.6 with Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message:
The form contains some errors,[...] could not save change request[...] java.util.NoSuchElementException: key not found: MY_NEW_ATTRIBUTE_WITHOUT_VALUE

To add value to the new attribute, I need to save the Directive with the new version of the Technique but this error message prevent me to do it.

Actions
Copy link
 #1

Updated by Nicolas PERRON about 11 years ago

  • Priority changed from 1 (highest) to 3
  • Target version changed from 2.6.9 to 2.6.10
Actions
Copy link
 #2

Updated by Nicolas CHARLES about 11 years ago

You should never never change attribute names without changing technique version. That's why you are having this issue

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.10 to 2.6.11
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions
Copy link
 #7

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions
Copy link
 #8

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions
Copy link
 #9

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions
Copy link
 #10

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions
Copy link
 #12

Updated by François ARMAND almost 10 years ago

  • Subject changed from On Rudder 2.6 with Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message to With Workflow activated, upgrading a Technique code with changes in the attributes in the same version return an error message
  • Status changed from New to Discussion
  • Priority changed from 3 to 5 (lowest)
  • Target version changed from 2.6.20 to 2.10.10

Not sur what to do about that, because it's a edge case (changing a Technique without changing its version but with workflows enables... )

Setting a low priority on it. The solution would be to have a full verisonning on Technique independant of the "human facing" version.

Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.20 to 2.11.18
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #35

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #36

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #37

Updated by François ARMAND over 7 years ago

  • Status changed from Discussion to Rejected
  • Priority set to 0

I'm closing that ticket because it is not a supported feature. We don't allow to change a mandatory technique attribute name without changing the technique version.

Actions
Copy link

Also available in: Atom PDF