En mi cronograma las epic no muestran incidencias secundarias cuando utilizo el filtro de etiqueta
Asked by Eduardo Gaggero:

Hola.   

En mi cronograma las epic no muestran incidencias secundarias cuando utilizo el filtro de etiqueta.

Ac? el cronograma sin etiquetas:  
![1.png](/t5/image/serverpage/image-id/331966i02091CD08531692C/image-size/large?v=v2&px=999 "1.png")

Ac? el mismo cronograma al filtrar por etiqueta (solo 1):

![2.png](/t5/image/serverpage/image-id/331968iC8D0D2F955666140/image-size/large?v=v2&px=999 "2.png")

?El funcionamiento es as?? o hay algo que estoy haciendo mal?

Desde ya muchas gracias.


Answers:
author: Trudy Claspill
body: Hola [@Eduardo Gaggero](/t5/user/viewprofilepage/user-id/5470305) ,

Cuando aplica un filtro, solo se mostrar?n los problemas que coincidan directamente con ese filtro. No mostrar? todas las Epics que coincidan con el filtro, adem?s de todos sus hijos.

Si los problemas secundarios no coinciden directamente con el filtro, no se mostrar?n cuando se aplique el filtro.

---

Hello,

When you apply a filter, only the issues that directly match that filter will be shown. It will not show all the Epics that match the filter, plus all their children.

If the child issues do not directly match the filter then they will not be shown when the filter is applied.

> In my timeline the epics do not show secondary incidents when I use the tag filter
>
> Hello.
>
> <br />
>
> In my timeline the epics do not show secondary issues when I use the tag filter.
>
> Here is the schedule without labels:
>
> Here is the same schedule when filtering by tag (only 1):
>
> Is it how it works? or is there something I'm doing wrong?
>
> From already thank you very much.

comments: author: Eduardo Gaggero
body: Comprendo, deber? trabajar sin filtrar por etiquetas para ver las incidencias secundarias, muchas gracias.

pd: ?podr?an considerarlo como una mejora a futuro?

Saludos!


author: Trudy Claspill
body: No soy miembro del equipo de producto de Atlassian. No tengo ninguna aportaci?n especial para la priorizaci?n de su acumulaci?n de solicitudes de cambio.

Si desea brindarles esos comentarios, puede hacerlo haciendo clic en el bot?n Comentarios disponible dentro de la aplicaci?n.

![Screenshot 2024-06-26 at 3.44.23?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/331983iC71FA6269C338296/image-dimensions/280x329?v=v2 "Screenshot 2024-06-26 at 3.44.23?PM.png")

---

I am not a member of the Atlassian product team. I have no special input to the prioritization of their backlog of change requests.

If you would like to provide that feedback to them, you can do so by clicking on the Feedback button available within the application.

> I understand, I will have to work without filtering by tags to see the secondary incidents, thank you very much.
>
> PS: Could you consider it as an improvement in the future?
>
> Greetings!


author: Eduardo Gaggero
body: gracias [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)


author: Joseph Chung Yin
body: [@Eduardo Gaggero](/t5/user/viewprofilepage/user-id/5470305) -

I agreed with [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) suggestion. The key is that when one uses the filter, the used filter criteria must be present in all the issues that you want to see. The plan will not display the issues if the criteria don't apply to. This is often missed by users using the tool.

Hope this also helps.

Best, Joseph Chung Yin

comments: author: Eduardo Gaggero
body: gracias!


Tags: cloud

jira-service-management

jira-service-management-cloud