Hi everyone, I’m back with a Compass announcement that I hope brings you some good cheer in the holiday season.
Today, we are releasing custom component types in Compass on the Standard and Premium plans. Out of the box we still support the component types you know and love, and now you can create your own as well.
As a reminder, component types help you categorize your components. You can add custom fields to specific types, along with assigning scorecard by type. We’ve been getting requests for custom component types since Compass launched and I’m so pleased it’s finally available for you to use. Now you can track UI components, AI bots, business processes, or any other component type your company relies on, and match the language used in your internal tools.
Custom component types are managed by admins. Click the Settings wheel in the top right corner of your screen and find “Component types” on the left navigation bar.
Here you will see a list of all your existing component types, along with a prompt to create new ones. Custom types have a Name, Description and Icon, and can be used the same way that predefined types are used in Compass today. (Since it’s a new feature, there are a few limitations that are outlined below.)
After the custom type is created, you’ll be able to use it for newly created components, when switching an existing component’s type, and in the Component list view “Type” filter.
You can edit the name, description and icon of a custom component type on the “Component Types” page under settings, by clicking the ellipse (…) next to the component in question and selecting “Edit.”
To delete a custom type, you first need to migrate all components with that type to a different type. This can be done as part of the Delete flow. Click “Delete” and the below pop up will appear:
Select your new type, click “Change and delete type” and all components from the deleted type will move to the new type. For example, in the above image I am deleting the component type “AI Bot” and migrating all AI Bot components to the Service type.
Note: You can only migrate 500 components to a new type at once. Let us know if this becomes an issue and we can look at raising the limit. Also, component type deletion is permanent, so be really sure of your choice before you click that delete button.
What’s not ready yet?
In Jira software projects, components with custom types will be usable, but the icon will render as “Other” until we get it updated. Public Feature Request
Custom Types are not available in the Gitlab Forge app importer yet (although you can import components then change their type after creation.) Public Feature Request
Config as Code is not supported yet, in that you can’t use custom type ARIs in your yml files. We’ll work on this as a priority in January. Public Feature Request
How many custom types can I create?
The Standard plan comes with 3 custom types and the Premium plan includes 14.
What happens if I downgrade my plan?
If you downgrade your plan but have more custom types than your new plan allows, you will be able to continue using your existing components, but you won’t be able to add new components to the custom types or edit the types themselves, until you meet the limit for your plan.
Does this affect the Jira Service Management integration?
In Jira Service Management, components of type Service, Application and Capability will continue to be synced. At this time you cannot sync custom types. Let us know if this is something you’re interested in.
I’d love it if you could try this out and let us know what you think. What would you like to see next from custom types? Would you want to edit the built-in component types as well? Please share your thoughts and feedback on this blog post.
If you wish to share further feedback about Compass, please join our Compass Research Panel or email our researcher Caylie directly (cpanuccio@atlassian.com).
Have a great holiday season, and thanks again for using Compass.
Katie Silver
0 comments