Some custom field clauses when used singularly screw up the switch from Advanced to Simple

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 4

      • Cascading Select, Multi Checkbox and Multi Select all "fit" when the NOT EQUALS operator is used, when clearly they shouldn't.
      • The input for the ProjectPicker searcher is not populated with the value from the clause

            Assignee:
            Michael Tokar
            Reporter:
            Michael Tokar
            Archiver:
            Michael Andreacchio

              Created:
              Updated:
              Resolved:
              Archived:

                Estimated:
                Original Estimate - 1h Original Estimate - 1h
                1h
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 2h
                2h