Triggers in a Template based configuration

Template based configurations don't allow any triggers to be assigned unless they are in the template. This seems wrong since if projects A and B are based on Template T, then there is no way to tell project B to start after project A because doing so in the template would trigger A in a loop.

The only way is detaching from template for either A or B which seems to be a non-optimal solution for a problem like this.

1 comment
Comment actions Permalink

This is a known limitation, and we hope to fix it in the next minor release.


Please sign in to leave a comment.