Structure Gantt - Grouping by Sprint includes Closed Sprints

[Lexi]

I am using sprint grouping for my schedule, but when I move an item to the next sprint and the previous sprint is still listed on the JIRA issue, the JIRA issue will show up twice, once in the open sprint and again in a section for the closed sprint. I dont want to see the closed sprints in the my structure, it makes it too big, intorduces duplicates and makes the dependencies look really messy in the chart and hard to follow, how do I get rid of them?

[Florian Bonniec · Accepted solution]

Hi @Lexi 

You can Group by Sprint but then Apply a Filter on Sprint. You can select if you want to display, Closed, Future or Active Sprints.

https://wiki.almworks.com/documentation/structure/8.3/data-center-and-server/filter-generators-161843022.html

Regards

[Lexi]

unfortunately, that does not address the problem, the issues are in both a closed sprint and an open sprint, so nothing changes when that filter is applied.

[Stepan Kholodov _Tempo_]

Hello @Lexi 

The Hide Closed Sprints Filter generator indeed shouldn't remove anything in a structure because of the order in which the different types of generators are executed. Filters run before groupers, so a Filter generator can't remove any groups, created by a Group generator. But you can achieve it with the Hide Closed Sprints Filter transformation. You can find more instructions on how to use it in our Wiki here: https://wiki.almworks.com/documentation/structure/8.3/data-center-and-server/using-transformations-32223323.html

Best regards,
Stepan Kholodov
Tempo

[Lexi]

@Stepan Kholodov _Tempo_i turned on the "Hide Closed Sprints" transformation but it made no difference; For example, my May sprint is still showing right up at the top and I closed that out on June first. Is it supposed to remove the closed sprint groupings like I am looking for, or something else?

The link you sent me doesn't mention anything about the Hide Closed Sprints transformation.

I searched the site you linked and didnt find anything showing how it works.

[Stepan Kholodov _Tempo_]

@Lexi
The shared link indeed doesn't have anything specifically about the Hide Closed Sprint filter transformation; it is about how to use transformations in general. In case you haven't used them before, the documentation can be helpful and provide the how-to instructions.

As for the filtering results - if you have grouping by Sprints enabled and closed Sprints are not being removed after you turn on the Hide Closed Sprints transformation, then there might be some sort of a problem that requires investigation. Please submit a support request at our portal and we'll look into it.

Best regards,
Stepan Kholodov
Tempo

[Lexi]

Stephen, I am still poking around, but I think the order you put then in in the bar does matter; when I have the group before the filter, it seems like it's working. When I have the group after the filter, it doesn't work.

I think this should work for me.

[Lexi]

ok, i do still have several instances of this not working no matter where the filter goes, so i will put in a ticket and try to update here with the resolution

[Lexi]

resolution is to ensure that you use a very specific level ID settings for hide sprint

"all" will not work in all cases:

from support:

In your case, you need to specify the 3rd level because you are using other automation to build a hierarchy to your Structure, which creates some rules. As you have groupings being applied before the issues, Structure will not break the hierarchy that is being built. The filter must “see” the information related to Sprints that are in the issues, the grouping doesn't have the same information, so for this reason, the filter needs to be applied to the 3rd level.

[Lexi]

Anyone else have any solution for this?