You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am currently in the process of investigating the best way to configure Jira for our Product and Engineering teams going forward. We have opted to configure a next gen project for our discovery work and a separate project for delivery work.
We will soon be establishing squads who will work on objectives set by product on a quarterly basis. These squads will be reassembled each quarter.
All of the work carried out will be for our core product, as such we have opted to have one Project for delivery work.
Ideally we would like to structure the project so that multiple squads have a shared backlog but their own view of the board to see work that only pertains to them. Is that possible using next-gen projects?
Hi @Andrew Dunne ! Up to now, we have been focusing on making next-gen a great experience for the single team use case. Although great news is we are soon going to be switching our focus to the multi-team use case like the one you have described.
It is possible in the short to add team name as a label to each issue - and then filter the board by labels. Each team member could save the URL of the filtered board as a browser bookmark to save them filtering every time. Obviously this is just a workaround and we will have a better to do this in the future but it might just get you going. Let me know if you come up with other ideas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.