Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • stacks stacks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 173
    • Issues 173
    • List
    • Boards
    • Service Desk
    • Milestones
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • YourHeadYourHead
  • stacksstacks
  • Issues
  • #547
Closed
Open
Issue created Jul 15, 2020 by Ricardo@rjrggr

Conditionals not evaluating as expected

For example, let's say you have a custom item with the id test_value of type select and the possible values are for this custom type are, for example, 0, 1, 2 or 3 of type number .

In versions prior to v4.1, you could evaluate a statement to test the value of 0 (zero) as follows:

%[if !%id=test_value%]% it returns true if test value was 0 and false if anything else.

However in version 4.1 you get the following results:

%[if !%id=test_value%]% should return true, if test value was 0 and false if anything else (1,2 or 3). But it in actuality it returns true if the value is 0 2 or 3.

I am attaching a sample stack: Axyn_test_conditional2.stack.zip

Assignee
Assign to
Time tracking