- Set up a behaviour and select an applicable guide workflow.
- Use the UI conditions to set some field as read-only, with an except condition specifying that the issue must not be in the initial step (not status) of the workflow.
- Open the Create Issue screen in a project where the behaviour is mapped.
Expected: The except condition passes and the field remains writeable.
Actual: The condition fails and the field becomes read-only.
This happens because the Behaviours backend tries to compare the step ID as configured by the user (usually a small-valued Integer) with the status ID associated with the initial step (usually a large-valued integer converted to a String). This only happens during issue creation.