Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Board vs Connection types: possible Global vs Local types?

Mike Theis
Contributor
July 21, 2025

Hello again, another product suggestion for managing Types within workspaces while using the connections feature across workspaces. It would be great if we could allow Types to be global in our environment to allow for connections across boards easily, but then allow workspace managers to select which types can be created at the workspace level as a way to reduce the amount of options and information being presented within a teams backlog but also retain the ability to connect to a different workspace with that type. (types show up in the create option, filters, etc.)

This control would improve the overall connections experience and help boost our process governance while reducing confusion. Currently, users are managing items within their workspaces but also connecting via connections to other workspaces that might have different or unique types that team doesn't need nor want. We have had to restrict and centralize the Types we are allowing to allow for the connections feature to work, but it is still leading to some confusion. 

An example of this would be if the design team has their own workspace and would be collaborating with a data team. If they wanted to connect to items within each others spaces, they would need that connection type in their space too, leading to a less than desirable experience as the list of Types expands beyond what they actually use. Type = "Design Prototype" vs Type = "New API"  are not applicable to the opposite team for their backlogs, but discovery might connect the two teams together for shared work.

Additional context: 20+ workspaces in use, with 100+ cross-collaborators who don't always use the same definitions for things when conducting discovery. Universal Types that we have created across all of the spaces has helped, but now users are seeing types they don't use nor will ever use based on their discipline, but is available because they might connect to an issue of that type in the future.

Thanks for viewing and any suggestions anyone might have for this.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events