Epic Link dont show in Automation and Tasks created in backlog
Asked by Matheus Marques:

Hi all,

I've a project managed in jira cloud an we are facing some problems...  

1 - We are trying to create tasks and subtasks automated. Our configuration is working fine, but we can set our "EPIC" for this task:  

In this field, just some epics we don't know are visible  

![epic link.png](https://community.atlassian.com/t5/image/serverpage/image-id/281818i89CDB8AEFDF75368/image-size/large?v=v2&px=999 "epic link.png")  

2 - We are using Kanban board and when our automated tasks is created, this automatically is moved to backlog, we need to move it to main panel with "working/doing" status. How can we do it?  

![main panel.png](https://community.atlassian.com/t5/image/serverpage/image-id/281820i4D17DD412EBCF105/image-size/large?v=v2&px=999 "main panel.png")


Answers:
author: Giovanni Melai
body: Hi [@Matheus Marques](/t5/user/viewprofilepage/user-id/4625186),

1. Have you tried to type the name of the Epic in the field? By default the field shows a list of Epics that can be not relevant to you, but you can actually search the Epic you need by name.
2. Since you are using a Kanban board with the Backlog, I suspect the first status of the workflow is actually Backlog (that is mapped in the Board Backlog), you just need to transition the issue to the first status mapped in the Kanban, in your case it seems to be "A Fazer" ("To Do"), you can to it in the same automation.

I hope this helps

comments: author: Matheus Marques
body: Hi [@Giovanni Melai](/t5/user/viewprofilepage/user-id/86866) ,  

About my EPIC, when I try to search my EPIC in "**EPIC Link field** " he just doesn't show up and jira asks me to create a new epic with that name.  
When I try to insert my EPIC name in "**Epic Name field** ", I receive the following error:   
++Unknown fields defined during creation. They may be unavailable for the project/type. Check the custom field configuration. Ignored fields --++   
++Epic Name (customfield_10011)
![3.png](https://community.atlassian.com/t5/image/serverpage/image-id/282057i40BBFD48044243E1/image-size/large?v=v2&px=999 "3.png")++

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

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

I tried to change my flow to start a new task in "going/working" but it keeps in my backlog with working status:  

![1.png](https://community.atlassian.com/t5/image/serverpage/image-id/282056i4D8A8D139F36DD7D/image-size/large?v=v2&px=999 "1.png")  
![2.png](https://community.atlassian.com/t5/image/serverpage/image-id/282055i29D3B49CEFB137BF/image-size/large?v=v2&px=999 "2.png")  

Note: This automation and epics is on the same project  

<br />


author: Giovanni Melai
body: Hi [@Matheus Marques](/t5/user/viewprofilepage/user-id/4625186)

about the Epic Link I think there is a weird behavior in the search, for that specific thing I would suggest you open a ticket with Atlassian, it might be something related to your specific instance. I testes it also with the same Epic Name and it just works for me. Just to try a different thing before opening the request, can you try doing the search with the second part of the name: ARQSEC

About the Epic Name, that is correct because you cannot add it to a Task, you don't have the field configured on the Screen. Also, the Epic Name is not used anymore since it was recently merged into the Summary of the Epic. More on this topic can be found [here](https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562).

I just realized that you are using a team-managed project so what I wrote about the status change does not apply. I don't use many team-managed projects, but as far as I can see there is no way to automatically move the issue out of the Backlog. The easiest way I see is to disable the Backlog and keep only the Board.

I hope this helps


Tags: cloud

jira-software

jira-software-cloud