Strange behaviour when trying to consume multiple resources by a task (+dailymax issue)

[allter]

I'm trying to declare a joint activity (dev + ops, dev + qa, dev + lead etc)

I tried using effort (which consumes only one resource), duration (did not work for me at all), length (strange behaviour, see below).
Tried to specify { mandatory } , but it did not seem to change anything at all.

When using duration i receive warning (it is actually an error because it nullifies the effort):
Warning in scenario plan: Task TASK_ID has resource allocation requested, but did not get any resources assigned. Either use 'effort' to ensure allocations or use a higher 'priority'.

When using length I get the same warning/error as in the case of duration. But when I specify priority 1000 I get what i want (both resources are allocated and consumed). But if either resource(s) or task have limits, the consumed amount is silently truncated. For limits in a task the resulting effort is a length * number_of_resources . For limits in a resource the resulting effort is even more strange.

It seems that:

1. The limitations of the constraint solver should be documented for limits, effort, duration and length (possibly using a link to a special page)
2. When limits interfere with scheduling a task, issue a warning, and don't truncate efforts silently. You make a simple mistake and you get garbage numbers without knowing it.

I experimented with the following (those limits in resources silently truncate errors):

    resource dev "Dev" {
        limits { dailymax 4h }
    }

    resource qa "QA" {
        limits { dailymax 6h }
    }

# ...

    task test "Test IT" {
        allocate dev { mandatory }
        #effort 11h
        #duration 11h
        length 11h
        allocate qa {mandatory}
        priority 1000
        #limits { dailymax 2h }
    }