Structure plugin, complex grouping by version

Hnd_349rkv

I have a question similar to this but slightly different: 

https://community.atlassian.com/t5/Jira-questions/In-Structure-group-by-Fix-version-sub-items-do-not-comply-to/qaq-p/1155024?tempId=eyJvaWRjX2NvbnNlbnRfbGFuZ3VhZ2VfdmVyc2lvbiI6IjEuMCIsIm9pZGNfY29uc2VudF9ncmFudGVkX2F0IjoxNTc4NDA3MTAwODI4fQ%3D%3D

Basically I want to achieve the same result but I am not able to build up my structure bottom up due to using "extend with links" automation.

To elaborate the scenario further:

We have 4-5 jira projects which are worked on by 3 teams.

We also have another separate jira project to hold the higher level initiatives which are linked to epics from those 4-5 jira projects. Let's call this "program" .

Program

   |___ Initiative: Online Shop(version:2020Q1,2020Q2)
   |___ Initiative: Community(version:2020Q1,2020Q2)

Application A project
   |___ Epic: Authentication(version:2020Q1,2020Q2)
      |___ Story: Basic authentication(version:2020Q1)
      |___ Story: Keycloak integration(version:2020Q2)
      |___ Story: some other dummy story 
   |___ Epic: Deployment on Amazon(version:2020Q1,2020Q2)
      |___ Story: Cluster setup(version:2020Q2)
      |___ Story: Run xyz(version:2020Q1)

Application B Project
   |___ Epic: Integration with thirdparty(version:2020Q1,2020Q2)
      |___ Story: rest api(version:2020Q1)
      |___ Story: connectivity(version:2020Q2)
   |___ Epic: Order management(version:2020Q1,2020Q2)
      |___ Story: shopping cart(version:2020Q2)
      |___ Story: order fulfilment(version:2020Q1)

These initiatives have links (dependency) to epics from projects A and B.

   |___ Initiative: Online Shop
      |___depends on: Authentication
      |___depends on: Order Management
   |___ Initiative: Community
      |___depends on: Deployment on Amazon
      |___depends on: Integration with thirdparty

So eventually, what I'd like to see is the following STRUCTURE:

Program
2020Q1
   |___ Initiative: Online Shop
      |___Authentication
            |___ Story: Basic authentication(version:2020Q1)
      |___Order Management
            |___ Story: order fulfilment(version:2020Q1)
   |___ Initiative: Community
      |___Deployment on Amazon
            |___ Story: Run xyz(version:2020Q1)
      |___Integration with thirdparty
            |___ Story: rest api(version:2020Q1)
2020Q2
   |___ Initiative: Online Shop
      |___Authentication
            |___ Story: Keycloak integration(version:2020Q2)
            |___ Story: some other dummy story 
      |___Order Management
            |___ Story: shopping cart(version:2020Q2)
   |___ Initiative: Community
      |___Deployment on Amazon
            |___ Story: Cluster setup(version:2020Q2)
      |___Integration with thirdparty
            |___ Story: connectivity(version:2020Q2)

So far, I couldn't find a way to filter the stories (or the issues under epics) by version.
Do you have any suggestions?

 

Edit: I forgot to add that we are using Structure server version. Should be the latest one as we are trialing it.

Thanks

Egor Tasa [ALM Works]

Hi, 

You can apply the same approach as before (though this would be a little tricky with not very obvious settings).

1. Insert stories
2. Group by Epic
3. Group by link between Program and Epic, set grouper to consider other groups - need to consider Epics here
4. Change order of groupers, Epic grouper should be above link grouper.
5. Group by version
6. Change grouper by link to Group on level: Next level - it does not have to look at fixVersion grouper

This instruction is a bit more complex than needed, but you will see your structure forming while you are doing it step by step, and perhaps the logic of generators will be more obvious this way. Otherwise you can start with grouping by link at next level with consider other groups on, then just group by Epic and then group by Fix Version. 

Please, check if it works for you.

Regards,
Egor