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

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

Eduardo Gaggero June 26, 2024

Hola. 

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

Acá el cronograma sin etiquetas:
1.png

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

2.png

 

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

Desde ya muchas gracias. 

2 answers

2 accepted

2 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 26, 2024

Hola @Eduardo Gaggero ,

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.


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.

Eduardo Gaggero June 26, 2024

Comprendo, deberé trabajar sin filtrar por etiquetas para ver las incidencias secundarias, muchas gracias. 

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

Saludos!

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 26, 2024

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

 

---

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!

Like Eduardo Gaggero likes this
Eduardo Gaggero June 27, 2024

gracias @Trudy Claspill 

0 votes
Answer accepted
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 26, 2024

@Eduardo Gaggero -

I agreed with @Trudy Claspill 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

Eduardo Gaggero June 27, 2024

gracias!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events