Unable to have automation-created Stories include the epic link of the trigger issue

[Ethan Ferguson]

Hello, I am new to automation in Jira and am trying to get automation set up for my new projects.

I currently have one Automation that is working as expected, that's listed below:

1. When a Prospect Project ticket (newly created ticket type) is edited to have a Labels = Confirmed, then change the Issue Type to Epic and comment on the Epic "Confirmed"

I am trying to set up a second automation that will create new Stories that are linked to that epic. However, when I try to open up the Epic Link field, it says it's unable to retrieve the epics.

This is what I have so far on the second automation, but I'm stuck:

1. Trigger: When Issue Commented (all types)
2. If the type = Epic (JQL query)
3. Action Create Issue > Story
   1. I cannot set the Epic Link because when I choose that out of the "Choose Fields to Set" dropdown, there's an error that says:
      1. Failed to retrieve selections, please refresh the page and try again.

How can I get these newly created Stories to have the trigger issue (the Epic) linked in the Epic Link field on the Story?

Thank you all!!

[Rob Horan]

Make sure Epic Link is on the create screen for your target issue type.  (It would be good to ensure it is on the view screen as well)

Then make sure the automation rule sets Epic Link using "Copy from trigger issue"

[Ethan Ferguson]

Hi there. That was the first thing that I went to look for. However, that field for me is showing the error message from my original message. It doesn't matter if I refresh, close the application, or whatever else I could think of... that field won't populate any values for me:

[Rob Horan]

Are you copying an existing rule?  It looks like there is an open bug about this:

https://jira.atlassian.com/browse/JSWCLOUD-22890

Also see https://jira.atlassian.com/browse/JSWCLOUD-22494

[Ethan Ferguson]

No, I am creating a new rule from scratch. I have a scrum project controlled by the company level. Not sure if that matters. 

[Ethan Ferguson]

Maybe I'm trying for the wrong thing? I'm hoping to automatically create a child issue of the epic, so that it's linked appropriately. 

Automation converts a ticket to an Epic

Then another automation to create a child issue of that (converted) epic.

I hope that helps add some clarity.

[Bill Sheboy]

Hi @Ethan Ferguson 

Would you please post images of your complete rules.  That may provide context for the symptoms you are observing.  Thanks!

And...changing the issueType of something is not a trivial thing...which is why the UX has a specific function and code (i.e. Move) for this operation.  I find it likely that when changing the issueType within a rule, problems may occur.  An alternative to this is to create a new issue of the desired type, copying over the fields, and then abandoning (or deleting) the source issue.

Kind regards,
Bill

[Ethan Ferguson]

Hi Bill! Sorry for the delayed response. I will try that first thing tomorrow and will let you know!