Skip to content

Multiple values are allowed on execution not on definition

kainuk requested to merge (removed):no_multiple into master

A checkbox custom field can have multiple values. This does however not mean that an action provider can map one input to multiple outputs, as the following suggests Selection_017

The problem is that this creates a mapping that does not work on execution. This PR removes the multiple properties from the screen, so that it becomes a normal mapping. multiple_after

Merge request reports