nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Automation - Epic Link : Failed to retrieve selections, please refresh the page and try again.

Muhamad Zulhadi

Hello everyone

I want to make an automation rule for creating a task as a child issue from an epic.

Somehow, the Epic Link did not show any option.

there is no option when I opened the drop down

I've made sure that the Epic Link field is exist in the task screen

But the Epic Link still empty in automation rule.

Thank your for your help.

Accepted answers

All comments

Sandra Axelsdottir

Is it be possible that the Epic status is closed?

Please, note that the epic status is different from the issue status. You can add the epic status field to your screen to be sure.

Regards,

Sandra

Muhamad Zulhadi

Hi Sandra,
Thanks for your answer. I've tried your suggestion.

but it still give me a same result

Sandra Axelsdottir

I was reading through your question again and I'm not sure I understand.

In the rule setup is trying to do the following:

When an issue is created
And the issue type is : Customer Data
Then create issue of the type: Prospecting which should be linked to a specific Epic.

Is that correct?

What is confusing me from the images is that the Prospecting type is using the same icon as an Epic, so for a moment I got confused and thought you were creating an Epic

However, I tried the following, with Story instead of Customer data and Task instead of Prospecting and it worked fine. That is, I can link to a test Epic.

Screen Shot 2023-03-12 at 17.16.43.png

Based on this, there must be something that keeps you from seeing Epics in the drop down.

What type of projects do you have? Maybe this has to do with you using a service project or permissions related to the project in question.

dez.makowski

I am encountering the same issue. Interested in a solution!

Alexis Cyr Poirier

Same here, still no devloppement ?

Bill Sheboy

Hi @Alexis Cyr Poirier

If you are seeing this symptom I recommend working with your site admin to submit a ticket to the support team to take a look. Customers on paid Jira licenses can do that here: https://support.atlassian.com/contact/#/

Kind regards,
Bill

unknown

Same error here. It happens in multiple situations.

In one of those I figured out that deleting an organization from Jira Service Management which was used in an automation results in this error. I used a user condition here, reporter must be in organization X (and X got deleted via customers > delete organization).

You will recognize it in the automation where the ID is shown instead of the name. I would expect deleting an automation results in removing it from automations as well.

Result is you cannot make any changes anymore in the automation.

Still looking into the other situations.

unknown

For some reason I got this in my conditions:

{
"field": "reporter",
"check": "USER_IS",
"criteria": []
}

As fas as I know one cannot save the rule without having a reporter in place. But it ended up in the same situation. Since I could remove this condition and can proceed I will not dive into the cause of how this condition got there, but wanted to let you know it will result in the same error.

By the way. This one could be fixed via the interface. The removed organization(s) and ID situation required export > remove id manually > import to fix it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud