If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 28/Sep/22 08:53 PM
Updated: 21/Jan/23 01:15 PM
|
|
Component/s: |
None
|
Affects Version/s: |
12.0.18,
12.0.17,
12.0.16,
12.0.15,
12.0.14,
12.0.13,
12.0.12,
8.0.48,
12.0.11,
12.0.10,
12.0.9,
12.0.8,
12.0.7,
12.0.6,
12.0.5,
12.0.4,
12.0.3,
12.0.2,
12.0.1,
12.0.0,
8.0.47,
10.0.42,
11.0.33,
11.0.32,
11.0.31,
10.0.41,
11.0.30,
9.0.49,
10.0.40,
11.0.29,
11.0.28,
11.0.27,
11.0.26,
10.0.39,
11.0.25,
11.0.24,
11.0.23,
11.0.22,
10.0.38,
10.0.37,
11.0.21,
11.0.20,
10.0.36,
11.0.19,
10.0.35,
11.0.18,
11.0.17,
11.0.16,
11.0.15,
11.0.14,
11.0.13,
11.0.12,
11.0.11,
11.0.10,
11.0.9,
11.0.8,
8.0.45,
8.0.44,
11.0.7,
11.0.6,
11.0.5,
11.0.4,
8.0.43,
11.0.3,
11.0.2,
11.0.1,
11.0.0,
10.0.34,
10.0.33,
10.0.32,
10.0.31,
10.0.30,
10.0.29,
10.0.28,
10.0.27,
10.0.26,
10.0.25,
10.0.24,
9.0.48,
8.0.42,
9.0.47,
10.0.23,
10.0.22,
10.0.21,
10.0.20,
10.0.19,
10.0.17,
10.0.16,
10.0.15,
10.0.14,
10.0.13,
10.0.11,
10.0.10,
10.0.9,
10.0.8,
9.0.46,
10.0.7,
9.0.45,
9.0.44,
10.0.6,
10.0.5,
10.0.4,
9.0.43,
10.0.3,
10.0.2,
9.0.42,
10.0.1,
10.0.0,
9.0.41,
9.0.40
|
Fix Version/s: |
13.0.0,
13.0.2
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
When setting a variables value via code it does not reflect the change in the audit log. for example
at the root configuration create a variable called "TestVariableToUpdate" and give it a value of "correctValue". Then create a child configuration and add a step that updates the "TestVariableToUpdate" variable for example:
vars.get("TestVariableToUpdate").setValue("wrongValue")
When that configuration runs it would change the variable at the root configuration from CorrectValue to wrongValue; however, when you view the Audit log at the root configuration or the Administration tabs audit log; it does not tell you which configuration/step or configuration/variable was responsible for it being updated. This makes it extremely difficult to track down if someone incorrectly has a configuration that is changing a variable they are inheriting but should not be changing it's value from the inherited level and should only be changing it at their configuration's level. It would be ideal to have that information in the audit log or have a way to specify for the specific variable that if it is changed via code - to record the configuration and step or configuration and variable that changed it. This way variables we know should not be changed via code at the root level we can flag so if they accidently are it will have an audit record for us to easily track when the change was made and which configuration we need to correct so it doesn't happen again.
|
Description
|
When setting a variables value via code it does not reflect the change in the audit log. for example
at the root configuration create a variable called "TestVariableToUpdate" and give it a value of "correctValue". Then create a child configuration and add a step that updates the "TestVariableToUpdate" variable for example:
vars.get("TestVariableToUpdate").setValue("wrongValue")
When that configuration runs it would change the variable at the root configuration from CorrectValue to wrongValue; however, when you view the Audit log at the root configuration or the Administration tabs audit log; it does not tell you which configuration/step or configuration/variable was responsible for it being updated. This makes it extremely difficult to track down if someone incorrectly has a configuration that is changing a variable they are inheriting but should not be changing it's value from the inherited level and should only be changing it at their configuration's level. It would be ideal to have that information in the audit log or have a way to specify for the specific variable that if it is changed via code - to record the configuration and step or configuration and variable that changed it. This way variables we know should not be changed via code at the root level we can flag so if they accidently are it will have an audit record for us to easily track when the change was made and which configuration we need to correct so it doesn't happen again. |
Show » |
No work has yet been logged on this issue.
|
|