You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a step parameter provides the ability to use a custom expression, and one is provided
Then saving and reloading the step configuration will show the underlying control type, instead of the custom expression
Clicking use custom expression however will show that the underlying value is correctly still set.
This bug appears to exist in 2.6 and so is not a regression bug.
As the underlying value is still persisted it should not be a blocker for deployments.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.
lockbot
locked as resolved and limited conversation to collaborators
Nov 26, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If a step parameter provides the ability to use a custom expression, and one is provided
Then saving and reloading the step configuration will show the underlying control type, instead of the custom expression
Clicking use custom expression however will show that the underlying value is correctly still set.
This bug appears to exist in 2.6 and so is not a regression bug.
As the underlying value is still persisted it should not be a blocker for deployments.
The text was updated successfully, but these errors were encountered: