Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hey community,
i'll keep it short. We have several automation to give issues a proper status. The easiest one to understand is, if any issue within a parent or epic is in development, the parent oder epic has In Development status. This works as intended but it seems like an automation cannot trigger an automation.
Scenario: Keep proper status
Given: Automation rules to keep the status right
And: they are working if triggered by sub-task/sub-issue
When: we set a status for a sub-task to In Development
Then: The epic will transitioned to In Development
But this isn't working. Only the "higher/parent" issue will be updated. But there is no sub-task --> Epic relation.
(Working) Start from here:
I set the status of the sub-bug issue to in development and the parent issue (story) got the proper status as well.
When i set the status of the story to In development, the epic got the proper status as well
actually should the epic have the proper status as well because one of the subs is in development.
I don't get it :D Who can help me out?
Automation Rules:
Hi Sebastian,
Sorry, but I am not understanding your question. Thank you for sharing the screenshots - very helpful! But what is happening that shouldn't? Or should happen that is not happening?
Hey sorry if the description is insufficient.
When Sub-Task has status "In Development" --> Parent should have status "In Development" AND epic should have the status "In Development"
Automation 1: Sub-Task <> Parent relation
Automation 2: Parent <> Epic relation
GOAL: Epic <> Sub-Task relation by triggering both automations.
Automation 1 should trigger Automation 2 because of the conditions in Automation 2. But this is not happening.
BUT both of them are working separately as intended.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great! Thanks for that. Can you share a screen shot of the General Details of the rule for the second one that is not firing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We only have these 2 automation rules. I have assumed that there is an dependency.
Automation 1 can trigger automation 2 because of the conditions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep - but can you do the screenshot of your Rule details for the second one?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry i don't get it. I posted both automations above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There we go! That last one. Click the box for Allow rule trigger. Save and Publish. That should do the trick for you that when the Sub-task changes, it updates the Parent. When that Parent changes, it should now update the Epic automatically. :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are very welcome!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.