Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Muhamad Zulhadi March 9, 2023

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.

1.png

 

there is no option when I opened the drop down

3.png

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

4.png 5.png

But the Epic Link still empty in automation rule.

Thank your for your help.

5 answers

0 votes
Bart Dijkman
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 28, 2023

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.

Bart Dijkman
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 28, 2023

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.

0 votes
Alexis Cyr Poirier
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 13, 2023

Same here, still no devloppement ?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 13, 2023

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

0 votes
dez.makowski
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 21, 2023

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

0 votes
Sandra Axelsdottir
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 12, 2023

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

In the rule setup is trying to do the following:

  1. When an issue is created
  2. And the issue type is : Customer Data
  3. 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.

0 votes
Sandra Axelsdottir
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 9, 2023

Hi

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 March 9, 2023

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

 

but it still give me a same result

7.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, atlassian government cloud, fedramp, webinar, register for webinar, atlassian cloud webinar, fedramp moderate offering, work faster with cloud

Unlocking the future with Atlassian Government Cloud ☁️

Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.

Register Now
AUG Leaders

Upcoming Jira Events