Unable to find epic in epiclink during automation
Asked by Marcus Chuah:

Hi all,

I have multiple projects in my team and there is one specific Epic that i am trying to link towards as part of my automation. However, i am unable to find that specific project Epic in this page. Other projects epic do show up, is this due to some sort of settings?

I will like to add an Epic from the IS project. Images of the different project types are available below.

Thank you.

![Screenshot 2022-02-17 at 13.58.20.png](https://community.atlassian.com/t5/image/serverpage/image-id/183913i6EBB76E0CE9B8CC9/image-size/large?v=v2&px=999 "Screenshot 2022-02-17 at 13.58.20.png")![Screenshot 2022-02-17 at 14.00.37.png](https://community.atlassian.com/t5/image/serverpage/image-id/183914iFAD57BA171EDCB78/image-size/large?v=v2&px=999 "Screenshot 2022-02-17 at 14.00.37.png")


Answers:
author: Stefan Salzl
body: Hi [@Marcus Chuah](/t5/user/viewprofilepage/user-id/4761598) ,

Could you provide a screenshot of the "rule details" and also from your EPIC you want to link to?

Best  
Stefan

comments: author: Mykenna Cepek
body: [@Marcus Chuah](/t5/user/viewprofilepage/user-id/4761598): ensure that the project which contains the Epic is configured for the rule.


author: Stefan Salzl
body: [@Mykenna Cepek](/t5/user/viewprofilepage/user-id/3527113)

I was thinking of the sope of the rule (single vs multi project) but as the screenshot shows and I tested on my site also single project rules show epics from other projects.

Which configuration would need to be done? Could that be a permission configuration that avoids linking to a certain project??

Best  
Stefan


author: Mykenna Cepek
body: I've had difficulty with rules that try to access issues outside the Projects configured for that rule. I answered a different Community question recently where I tested just that. The rule didn't work until the Scope/Projects under "Rule details" included Projects for all issues of interest. "All projects" (global) scope would be fine too.

Maybe there are some edge-cases where rules confined to specific projects can indeed "reach out" to issues in other projects. I doubt that, but even if it was true, I wouldn't rely on that behavior.

It's an easy test for [@Marcus Chuah](/t5/user/viewprofilepage/user-id/4761598) to try: expand the scope of the rule and see if that fixes it.

In theory, permissions could indeed relate. If a non-admin, for example, is configuring rules, and doesn't have privs to see or access another project, then they might be unable to configure the rule scope properly.


author: Stefan Salzl
body: The scope was my first guess. As I tested it in my setting and it worked here I deleted this guess from my question =)

As you mentioned: The good thing is this can be tested very easily :)

Thanks for your description. Reminded me of not always using the admin user :)


author: Marcus Chuah
body: Thanks all it works now, its just the automation was not applied to the specific project.


author: Stefan Salzl
body: Nice. Glad to know it works now.

Best  
Stefan


author: Pramodh M
body: Hi [@Marcus Chuah](/t5/user/viewprofilepage/user-id/4761598)

Did you search the Epic by typing Epic Name? **Type the FULL EPIC KEY**

Even if the Epic is from team-managed to company-managed or vice versa you should be able to link the Epic.

![Epic Link.png](https://community.atlassian.com/t5/image/serverpage/image-id/183916i4FB7B4BAA031220C/image-size/large?v=v2&px=999 "Epic Link.png")

Thanks

comments: author: Marcus Chuah
body: Hi [@Pramodh M](/t5/user/viewprofilepage/user-id/3691224) ,

Thanks for the reply.

I did key in the Epic name but i get the error failed to retrieve selections. Thank you.

![Screenshot 2022-02-17 at 15.01.10.png](https://community.atlassian.com/t5/image/serverpage/image-id/183920iADEFA35BA939A861/image-size/large?v=v2&px=999 "Screenshot 2022-02-17 at 15.01.10.png")![Screenshot 2022-02-17 at 15.00.57.png](https://community.atlassian.com/t5/image/serverpage/image-id/183921i746141862285F131/image-size/large?v=v2&px=999 "Screenshot 2022-02-17 at 15.00.57.png")