New "Group By" Board Filter for kanban/Scrum Board

[#1]

Hello Community Member,

Jira has once again stepped up to the plate with a game-changing feature: the "Group By" board filter.

Users can customize groupings based on a wide range of attributes, including assignee, Story, Epic, and queries. This flexibility empowers teams to tailor their project boards to suit their unique needs and preferences, fostering a more intuitive and efficient working environment.

As an Atlassian Creator and ACE Leader, I've made this video tutorial to help you better understand this new feature. You can watch my full video to learn how you can use this and where you find it onboard view. https://youtu.be/MFfyw9kU_Uk

Leave comments on what you think about this cool feature.

[Alex Hall]

I just had a user report a bug regarding this feature.

• Our Board Swimlanes use the Assignee method
• When new Users first navigate to the Board, their "GROUP BY" displays "None", however, since the Board is set by Assignee, the Swimlanes are organized by Assignee.
• When the Users use the drop down and change it from "None" to "None", all of a sudden they no longer see the default Board Swimlane setting, and it's organized with no Swimlanes. This setting appears sticky after the first time users select this. And this setting now permanently overrides the Board Swimlane method
• I have only been able to observe this on a Board, which was initiated presumably during the rollout for this feature. I started the Project/Board between May/June.
  
  • All our older Boards properly sync the GROUP BY setting with what is actually seen on screen.
  • When I create a new Board, the sync is also in place.

[Taqveem Mohammad Khalid]

Awesome, this is exactly what we needed in our team!

[Marc - Devoteam]

Hi @Monika Rani 

The same issue, reported by @Alex Hall is happening on my personal instance , my companies instance and instances where I'm working on as Consultancy projects.

Swim lane settings are completely not working anymore.

I see there is a Bug reported on this, JSWCLOUD-26927 , can this be given priority?