"IF / Else" does not support null on secondary input in workflow builder GUI #756

Closed
opened 2026-04-05 16:22:45 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Kuldran on 8/6/2024

Describe the bug
you cannot use an if/else block to do a null object check.

To Reproduce
Steps to reproduce the behavior:

  • Create a find incident block (look for something that returns null?)
  • Link it to a if option
  • In an if statement set param 1 as object, and param 2 null cannot be specified for 'Equals to' and not

Expected behavior
Should be able to check for null.

Screenshots
image

Desktop (please complete the following information):

  • Browser chrome, chromium, firefox-sre
  • Version what ever is on debian sid.

Deployment Type
tested on self hosted

Additional context
see slack for info.

*Originally created by @Kuldran on 8/6/2024* **Describe the bug** you cannot use an if/else block to do a null object check. **To Reproduce** Steps to reproduce the behavior: - Create a find incident block (look for something that returns null?) - Link it to a if option - In an if statement set param 1 as object, and param 2 null cannot be specified for 'Equals to' and not **Expected behavior** Should be able to check for null. **Screenshots** ![image](https://github.com/user-attachments/assets/d6fc8e7c-142a-4703-9f41-20682662935e) **Desktop (please complete the following information):** - Browser chrome, chromium, firefox-sre - Version what ever is on debian sid. **Deployment Type** tested on self hosted **Additional context** see slack for info.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#756