Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-1680

Auto-suggest values for Boolean Smart Values

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      When using IF Conditions, adding a Boolean Smart Value (such as page.hasEmptyBody) under First value allows users for entering any text under Second value.

      In such cases, it would be helpful to pre-populate the available values (such as 'true' and 'false') and transform the text field into a drop-down selector in order to avoid errors when creating the condition.

      This is specially helpful as those values are currently case-sensitive and will only accept lower-case 'true' and 'false' as mentioned in AUTO-1679.

      Suggested Solution

      Pre-populate the Second value field when Smart Variable entered on First value is a Boolean (or has limited options for values such as 'null').

      Workaround

      Currently there is no workaround available.

        1. Screenshot 2025-02-10 at 17.18.49.png
          Screenshot 2025-02-10 at 17.18.49.png
          90 kB

            [AUTO-1680] Auto-suggest values for Boolean Smart Values

            Bill Sheboy added a comment - - edited

            Greetings!

            When considering suggestions like this, please consider their impact on rule-writers productivity.  Specifically, do not add auto-complete features unless the feature can be disabled for the automation rule editor at the Site and Project scope.

            My reasoning the rule editor already has performance problems.  Adding a feature that dynamically shows text, probably with latency, that obscures what the rule-writing is typing will only slow people down.  They will likely spend more time pressing the Backspace to clear the auto-complete to type what they actually wanted.

            Kind regards,
            Bill

            Bill Sheboy added a comment - - edited Greetings! When considering suggestions like this, please consider their impact on rule-writers productivity.  Specifically, do not add auto-complete features unless the feature can be disabled for the automation rule editor at the Site and Project scope. My reasoning the rule editor already has performance problems.  Adding a feature that dynamically shows text, probably with latency, that obscures what the rule-writing is typing will only slow people down.  They will likely spend more time pressing the Backspace to clear the auto-complete to type what they actually wanted. Kind regards, Bill

              Unassigned Unassigned
              tpallaro@atlassian.com Thiago P [Atlassian Support]
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: