Skip to content

Criteria expressions always use string comparison #3

@shadeon

Description

@shadeon

An age old one this - the UI that creates Expressions for use in the Criteria tab of many templates (ours included) always creates XPathQuery and ValueExpression elements with Type='String' set. This makes it hard and non-intuitive to create criteria based on numeric data, as any Greater/less than operators don't function as expected.

In order to resolve this, this UI page should be replaced with a new version that allows you to set the type when adding/editing each expression (note this needs to support multiple expressions, so should probably do so inline rather than a global dropdown or 'alternate' template that's hard coded to do decimal say).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions