Is there a way to limit the number of children cards that a parent card can have?

For example, when I set up a Release card, I would like to set a limit of 20 cards (stories) that can be added to that release. If me or somebody else tries to add one more card to the release card, I want Mingle to prevent it, notify me or ideally, automatically move the card to the next release card that has not reached the limit.

Is this possible? or is there a way to emulate this?

Hello,

Is there some way to reset the job status from a task?

While running tasks in a job, we have certain tasks that fail fairly often (2 or 3 times a day), but can be re-run and succeed (in this case it is a compiler error, and it usually succeeds on a second run).

For instance, we have something like this:

1. Build Code.

2. On Failed, Build Code (again).

3. On Failed, Send detailed Error to team.

4. On Passed, Do the rest of the tasks.

What we would like to have happen is that, when the first "Build Code" task fails (task 1 above), try to build the code again (Task 2 above).  If the second "Build Code" task fails, send a detailed error to the team (Task 3 above).  But if Task 2 succeeds, we'd like to skip task 3, and run task 4 (and the rest of the Success tasks).

What currently happens: once the first Build Code task fails, the second Build Code task runs.  Whether it succeeds or fails, only the "on Failed" tasks will run from then on.  So, the team ends up getting a detailed error message about a build that actually succeeded on re-run (which is resulting in confusing emails that must be carefully scanned to figure out what went wrong, on a job that's really already succeeded, and just needs to be re-run to allow it to go through all of the "on success" tasks).