UX for issue boards and team-first collaboration

We would like to learn how our users are using issue boards:

• Our product strategy is to push for issue boards as a workflow tool, and not as an organizational tool, as described in https://gitlab.com/gitlab-org/gitlab-ce/issues/25698. How do we better understand user needs along this demarcation? How are users using issue boards currently along these two vectors? How can we improve expectations?
• Issue boards are currently project-based, and focused on single repo use cases. We want to leverage issue boards to expand our product into the team-collaboration realm. So team-first use cases as opposed to repo-first use cases. What do users care about with regard to team-collaboration? How can issue boards move in this direction? https://gitlab.com/gitlab-org/gitlab-ee/issues/1295.
• Group level issue boards are an obvious first stab at team-first use cases. Is this the best approach? Any alternatives? Should group labels be used for group-level issue boards? https://gitlab.com/gitlab-org/gitlab-ee/issues/928
• How are users using GitLab as a whole? In regards to single repo use cases versus team-first use cases? How do we better integrate issues and issue boards together?

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.