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
I've seen some threads with this same question, but I cannot put my hands around this automation.
MY RULE
What am I doing wrong?
Current issue is the issue that is been evaluated in that loop so you are taking the value from the same child issue story and could be empy. You need to copy the value from the parent.
Thanks Jorge. I'm still new to automations so could you give me a visual? Sorry
The Epic will always have the component value and that is what I want passed down to the stories/spikes/tasks/subtasks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Gail,
What is not working for you? Does Jorge's change make it work for you? Or is it something else?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you change it to do what Jorge suggested? Meaning instead of copying the Component from the current issue to the trigger issue or the parent?
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.
Go into you rule to the Components step.
Click on the works "current issue" and change that to Trigger issue or Parent issue
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.
Let us know if that fixed the problem for you. :-)
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.
Great! And Go Steelers :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk can you pls help on this
I've encountered an issue with a Jira Cloud automation rule, and I'm hoping someone can help me resolve it.
I've set up an automation rule to count field changes in an issue from Monday to Friday. However, it appears that the rule is also counting changes on Saturday and Sunday, which is not the intended behavior.
Is there a way to configure the automation rule to exclude weekends (Saturday and Sunday) from the count? I want it to operate strictly on weekdays.
Any guidance or suggestions on how to achieve this would be greatly appreciated.
Thank you in advance for your assistance!
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.