Card #295 · Atlassian Marketplace
Inability to set task dependencies via automation rules
Users are unable to automatically establish dependencies or blockers for tasks and subtasks created through automation rules. This forces merchants to manually add dependencies, which is time-consuming and prone to human error.
Pain score
0.77/ 1.00 · weighted product of four components
Reach0.86distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement1.00upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 4 verified quotes
I can set dependencies with templates, but can’t create set a dependency on a subtask in a custom rule process.
Inside those sets tasks should have dependencies, but I cannot set them when i set up rule for adding those sets.
A rule seems to do all of these things except create the dependency between the new task and the trigger task.
At the moment I can’t add any blockers to these subtasks within the rule. Instead I would have to manually add blockers each time which isn’t great when we are trying to automate everything.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro