You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Looking for some automation rule help - I have a rule for when an Epic change 2 custom fields (Project & Work Type) then populate that value on all the Epic children. My rule won't populate the sub-tasks though. Suggestions on how to make the rule work for all Epic child cards & Sub-tasks?
Here is the rule that partially works:
Hi @Ann Rumenapp ,
As it seems your branch searches only for stories, try using JQL branch and using JQL "parentEpic = {{issue}}". The parentEpic function looks for all the tasks in the epic and their subtasks.
THANK YOU so much! That worked. I'm just learning/testing out how to write automation rules.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have a link to Atlassian documentation on branch search function options? I have another rule to update a card and it's sub-tasks that there is probably a function for
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good luck! Automation is fun.
The whole documentation for JQL is here https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/ . If you want to see the exact options, check out functions and fields section.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not enjoying this assignment for automation rules at all! I get one rule to work and then other rules conflict.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Today when running the automation rule, the audit log gives me this error on subtask cards: No fields or field values to edit for issues (could be due to some field values not existing in a given project)
I've checked the screen and field configurations which have the work type and project fields. Where else should I look to figure out this error?
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.