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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,528
Community Members
 
Community Events
175
Community Groups

I'm unable to set the Epic Link in an automation rule.

Danno Community Leader Dec 15, 2022

Help! Can someone explain my automation rule issue with the Epic Link? I'm getting this message when I try to add the Epic Link to the newly created issue.

"Found multiple fields with the same name and type: . Epic Link (com.pyxis.greenhopper.jira:gh-epic-link)"

Is this possibly due to the new Parent method that is to replace the Epic Name/Link existing method? (edited) 

3 answers

1 accepted

0 votes
Answer accepted
Jack Brickey Community Leader Dec 18, 2022

Hi @Danno , I would recommend reaching out to Atlassian Support on this. Please keep us posted on your findings.

0 votes
Danno Community Leader Dec 28, 2022

OK all, here's the deal. @Karoline Rezende Ramos I'm going to have to throw this one to @Jack Brickey as it was necessary to get rid of the "duplicate" system Epic link as opposed to trying to force it with field IDs.

The weird part is they didn't have a definitive answer as to how I got into this predicament in the first place. The belief is that it happens when you do a system restore. I'm grilling my contact for some more definitive answers.

I have moved Sandbox projects back to my main instance before but haven't noticed this being an issue in the past. All of the custom fields usually get displayed as (migrated) to give them a unique name. Very easy to run through and delete after the fact.

Hello @Danno

In your instance is there more than one custom field called "Epic Link"?
If so, I suggest using the ID instead of the field name.

If I understand your question correctly, if not, can you share more details?

Thanks.

Danno Community Leader Dec 15, 2022

Yes, I do have more than one Epic link although it only allows me to select one of them and it has the correct choice in it. I'm also working out how to try to change the field with smart values right now. I'll update as things progress.

 

Epic Link Issue Screenshot 2022-12-15 143849.png

Epic Link Issue Screenshot 2022-12-15 143849_2.png

Danno Community Leader Dec 15, 2022

So, I do have two Epic Link fields that are both Locked by the system. Can anyone explain how that happens?

Epic Link Issue Screenshot 2022-12-15 143849_3.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events