Our team handles a large volume of small projects running in parallel. We have, until now, used a single JIRA board with a filter query that includes all of these different projects to organize our work.
In the New JIRA experience, which we tried out last week, boards now belong to a single project. It is very hard to find a board unless you know which project the board belongs to and go into it through there. Additionally, when configuring boards, there is a new field called "Location" which requires that you place a board within either a project or a user profile.
What should be best practice moving forward for boards and projects? We cannot conceivably maintain 20 different boards; it would be ridiculous to try and work through those at a daily standup meeting. Can someone please shine some light on what Atlassian's goal with this change was, and what should be done with people like us who share multiple projects on a single board?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs