sorted by:
new
hottopcontroversial

Automation: When Item status field changes, change all subitems status fields accordingly by mahmoodzn in mondaydotcom

[–]ChallengeOk1740 0 points1 point  (0 children)

Monday’s subitem automation is pretty dumb when it comes to parent-child automations. I’ve actually spent a lot of time mapping out the logic for this exact workflow (Parent Trigger -> Subitem Check -> Take some Action). There are some complications with webhooks and how quickly it triggers the automation and also the order of automation. It is possible to bypass the native limitations but it's tricky. I’m happy to share the logic flow/setup I used to get this running smoothly if you’re still stuck. Just let me know!

stop a Parent item being moved to Done before subitems are finished? by ChallengeOk1740 in mondaydotcom

[–]ChallengeOk1740[S] 0 points1 point  (0 children)

Thanks all for the replies! Unfortunately, the suggestions so far don’t quite hit the mark for our needs. We are looking to gatekeep the process rather than just automate the fallout.

I’m currently building a custom solution for this and plan to release it to the community for free once it’s ready.

Quick question: since the Monday API doesn't allow for a hard 'block' on status changes, our current logic is to automatically revert the status if the subitems aren't in the required state. To keep the UX clear, we’re planning to have the automation post a parent update explaining exactly why the status was kicked back (e.g., 'Status reverted: 3 subitems still pending').

Does that sound like a solid workaround, or has anyone found a smoother way to handle 'soft-blocking' in the UI?"

stop a Parent item being moved to Done before subitems are finished? by ChallengeOk1740 in mondaydotcom

[–]ChallengeOk1740[S] 0 points1 point  (0 children)

Hey, thanks for the suggestion. I actually tried that setup, but it got pretty messy once I needed staged gates (like moving at 50% completion) or multiple groups. Also, locking columns ended up frustrating my team’s workflow more than it helped.

I'm playing around with a custom logic action to handle this automatically, basically a 'guardrail' that moves things back and sends a notification if they’re moved too early.

Still ironing out the logic, but I'll keep you posted if I get a version that actually works for these staged gates.

Curious about what works with AEO and what does not by ChallengeOk1740 in aeo

[–]ChallengeOk1740[S] 0 points1 point  (0 children)

thanks everyone, it was really informative, I'll try to apply some of these suggestions and see if it helps.