Hi Dear Community Members,
how do you handle aggregated boards? I find board location very confusing and limiting.
Many times I have several projects with their own boards and I want to create separate board that will aggregate all issues from those projects. I always have dillema where to set the location of new board:
Both of them are not perfect. First of all users want to get access to this aggregated board as easy as possible - so it should be accessible directly from every single project and not just one of them (so the later option is not ideal). I can create a shortcut to this aggtregated board (located in separate project or one of existing) on every project but that will move users away from the project they were using at the moment and in the long run make their work more difficult.
There are also another possibilities:
Am I missing something? How do you handle such configurations? What do you think is the best approach to such use cases?
Hi Atlassian Community, My name is Avni Barman, and I am a Product Manager on the Confluence Cloud team. Based on feedback from you, we are giving admins more power to create templates that a...
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