Skip to content

Conditions about Step / Action / Control are evaluated absolutely, not relatively #2643

Description

@InkUisitor

This type of condition generally works very well. The problem mainly arises when you place this type of condition in a Library and use it elsewhere.
The step used via the Library will not have the same position and will attempt to check the condition in absolute terms (which, in this case, makes no sense), whereas when used from a Library, it should be checked in relative terms.

For example:
Step 1 / Action 11 / Control 1, used via a Library, may become Step 12 / Action 11 / Control 1 in a real-world scenario. Except that it is indeed the absolute path that continues to be triggered

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions