Could you please help me configure the automation rule?
I have user stories within an Epic.
I break down user stories into tasks (not subtasks).
When I link a task to a User story as a child issue, I need the Epic link field to be automatically copied from User story into the task.
Here is one of the configurations, but it does not work, as well as the previous 50(((
It seems working when I tried the rule as below, while linking from Task to Story (I used 'is blocked by' relation here).
Thank you!
I tried to remake it for Parent to link, it didn't work. Then I tried reproducing your rule - but it did not work either. Looking at the logs I cannot see what is wrong - I definitely have Epic Link field on the screen for both User Stories and Tasks issue types, and User story is within an Epic. Any ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Yuliia ZhyliaievaI believe the EWCJ-10 is the Task and EWCJ-24 is the Story. ?
Can you share the screenshot of the 'Edit issue fields' part.
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.
EWCJ-10 is a story that has an Epic link, EWCJ-24 is a task that has an empty Epic link field that I want to update
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So it's the wrong issue that's been picked up by the rule.
Try adding link from Task, by setting relation like Task 'is blocked by' Story.
And see how it comes.
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.
Finally got it (printscreen above). Gikku_Mathew_John, thanks for supporting me through this experiment!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I also faced similar problem as @Yuliia Zhyliaieva Thank you both - for rising this issue and for the solving @Gikku :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.