Import components into your catalog

If you’ve connected Bitbucket or GitHub to Jira, components automatically populate in your Compass catalog based off of your connected Bitbucket workspace and/or GitHub organization. It also populates important metadata for these components, such as owner team, documentation, description, and repository events/activity.

When you add new repositories in Bitbucket or GitHub, they automatically import into Compass. If you want to add additional components, you can use the other import options listed below. However, you cannot import repositories separately from the Bitbucket or GitHub integrations once they have been auto-populated.

You can import components into Compass in bulk from applications that are external to Compass. Bulk import lets you start tracking many components at once, without having to add each component one by one.

You can import components from:

When you manually connect a Bitbucket or a GitHub repository to Compass, it will automatically scan the source code management (SCM) app for API documentation. If the scan finds API specifications in your repository, you can view endpoints on individual component pages.

You can’t import components of the capability, cloud resource, data pipeline, machine learning model, UI element, and website types from a connected app. We're working on adding this feature for components like this.

For now, create the component manually or use the API.

We recommend that you don't exceed 20,000 components in Compass, beyond which you may notice some performance degradation. We are working on scaling the solution to increase the limits over time.

Still need help?

The Atlassian Community is here for you.