Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to create to group issues by sprint in structure?


I have created a structure to view one team tasks. I have added group by sprint to the structure, but the view now is very confusing. What i want to see is all issues that were in sprint1 under sprint 1; all issues that were in sprint 2 under sprint 2. BUT in case an issue belongs to several sprints (e.g. sprint 1 and sprint 2) i will see "sprint1, sprint2" group.

I guess i need to use something else then Sprint field for grouping. Because right now grouping done by sprint filed, not by actual sprint.

Can someone advice what field need to be used? and how?

Br, Natalia

1 answer

Hi Natalia,

Thanks for posting.

You are on the right track, just missing one piece. In order to get the desired results, you can go about this 2 different ways:

1. Apply the Group by Sprint Generator to your current structure
2. Apply Transformation: Filter by Sprint - Hide Closed Sprints ( you must filter on "current level")

1. Create a new, empty structure
2. Insert your current structure into the new one. Please note that your current structure must already have a Grouping by Sprint. The reason for this is that Filters are executed before Groupers. (So if you insert your structure, add the Sprint Grouper and then apply the Filter, nothing will happen. )
3. Filter: Hide Closed Sprints (make sure to filter on "current level")

It works this way because Sprint Filtering is limited to inserted structure(s), not to the whole structure (which is why you have to use a Transformation in A.) and applies to Sprint Folders/Groups versus issues themselves.

I hope this helps. Please let me know if you have any additional questions or if you need further assistance.

Best Regards,


[ALM Works]

Hi Vlad,

Thank you very much!

Best regards,


Hi Natalia,

Here in both ways, Im not able to see spilled over tickets which got moved from closed sprint to Current Sprint (Active)


Is there a way to group in structure with Active Sprint name only.


Sadeesh N

For the benefit of others who may see this...

The beauty of Structure is that there are many ways to approach things like this (as Vlad's previous response points out).  It's a matter of choosing the best approach for your specific use case. 

@Sadeesh Narendran:  Have a look at my response in the other, related thread you created.  :) 

-dave [ALM Works]

Thanks @Dave Rosenlund _ALM Works_ & @Vlad-ALM Works- the above solution worked out for me, when i used the filter with choosing "Current Level".



Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

230 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you