Last updated Mar 28, 2024

Compass changelog

This page includes release notes and updates for Compass app developers. Use this page to keep track of new features, upcoming changes and deprecation notices about the Compass developer platform and GraphQL API.

Getting started

If you're new to building apps for Compass, check out Get started building Compass apps to begin your journey.

For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.

You may also be interested in the What's New blog for Atlassian Cloud where we announce new product features and other major changes affecting all users of Compass.

28 March 2024

Announcement Staged rollout started for Forge hosted storage data residency (beta)

We have started the rollout of data residency for Forge hosted storage, where data will be moving to the same location as the host product. To ensure a smooth rollout, we will be rolling out the feature to customers gradually over the next month.

Once the rollout is complete, Forge hosted storage data will be stored in the same location as the host product for all new and existing Forge apps, for all current and future Atlassian-supported locations. We will let you know when the rollout is complete.

Action Required
Last month, we outlined some actions required to prepare for this rollout (see changelog for more information). If you haven’t done so yet, we recommend:

  1. redeploying any app that uses Forge-hosted storage

  2. updating the manifest for any apps that use remotes or external permissions (for details about how to do this, see our documentation).

At the end of the staged rollout, we also recommend updating the Privacy & Security tab for any app that exclusively uses Forge hosted storage for in-scope End User Data, to indicate that your app supports data residency. You should also define in your app documentation what data is in-scope and out-of-scope. This way you can let customers know about your app’s support for data residency. We will let you know when to make this update.

More details

Data residency for Forge-hosted storage is the latest milestone on our shared mission to offer enterprise-ready apps to customers in the cloud. With data residency available for Forge-hosted storage, meeting a key customer trust requirement will be easier than ever.

It’s important to note that, as we shared last November, when data residency reaches beta for Forge-hosted storage, app data stored in Forge-hosted storage will automatically inherit data residency in all current and future regions supported by the host product. This will not be reversible.

Read more about data residency for Forge hosted storage.

5 March 2024

Announcement @forge/react version 10 release

As part of our preview release of Forge UI Kit 2, we're releasing a new major version of @forge/react with 37 updated components.

From version 10 onwards, existing component APIs are now updated, and a range of new components are now supported in UI Kit 2. For more details, see our documentation here.

The new version is supported within the following products:

  • Confluence

  • Jira

  • Bitbucket

  • Compass

Updating to the latest version may contain breaking changes for existing UI Kit 2 apps, as all existing component APIs have been updated. The breaking changes are only applicable if you choose to upgrade your UI Kit 2 apps.

Our component documentation contains more details on the props each component will now take.

To update your UI Kit 2 app to the latest version, in the terminal from your project directory, run the following command:

npm install --save @forge/react@latest

If you’re still using older versions of UI kit, such as the previous version of UI Kit 2 (@forge/react version 9) and UI Kit 1, you can find their corresponding documentation here.

1 February 2024

Deprecation Notice Deprecating appliedToComponentStats

The CompassScorecard field appliedToComponentStats is being deprecated in favor of scorecardScoreStatisticsHistories and criteriaScoreStatisticsHistories which provide historical statistics for scorecard scores and individual scorecard criteria scores. appliedToComponentStats will be removed on May 1, 2024.

More details

Why is this deprecation necessary?

This deprecation is necessary as we move to historical score statistics (scorecardScoreStatisticsHistories & criteriaScoreStatisticsHistories) for scorecards.

Dates and rollout

The new scorecardScoreStatisticsHistories and criteriaScoreStatisticsHistories fields are available now on CompassScorecard. The appliedToComponentStats field will be removed on May 1, 2024.

Migration guidance

The legacy appliedToComponentStats field contains the most recent snapshot of scorecard and criteria score statistics. The same data can be reconstructed using statistics histories, where the last statistic returned for each Histories field is the most recent.

For scorecard score statistics, use scorecardScoreStatisticsHistories. Each node in the connection (type CompassScorecardScoreStatisticsHistory) contains an array of CompassScorecardScoreStatistic’s, which hold component counts for a scoreStatus. The previously hardcoded statuses can be filtered out by matching on scoreStatus == "PASSING", "FAILING", or “NEEDS_ATTENTION".

For criteria score statistics, use criteriaScoreStatisticsHistories. Each node in the connection (type CompassScorecardCriteriaScoreStatisticsHistory) contains an array of CompassScorecardCriterionScoreStatistic’s, which hold the component counts for a scoreStatusStatistic. The previously hardcoded statuses can be filtered out by matching on scoreStatusStatistic == "PASSING", "FAILING", or “ERROR".

Test your updates to make sure the same functionality is maintained from appliedToComponentStats.

Once you have confirmed that your changes work as expected, remove any references to the deprecated field.

Known issues

There are no known issues with the migration process. However, if you encounter any issues during the migration, please consult the Support section below.

Support

If you need help with the migration or have any questions, please visit the Compass Announcement category in CDAC or chat with our support engineers by clicking the “Give feedback” button in the top nav bar on your Compass site.

Q&A

As we receive questions from developers and partners about the deprecation, we will update this section with answers to common questions. Please refer to the Support

22 December 2023

Announcement UI Kit 2 now supports Compass and Jira Service Management modules

You can now use Forge UI Kit 2 to build the user interface of your apps across all listed Compass modules and Jira Service Management (JSM) modules.

For more information on using UI Kit 2 components to design and build apps, see the UI Kit 2 components documentation.

8 November 2023

Removed Navigation to external links no longer requires additional confirmation

Selecting a link to an external resource immediately takes you there without showing a warning-style confirmation message.

19 May 2023

Deprecation Notice Deprecating createScorecardCriterias, updateScorecardCriterias and deleteScorecardCriterias Mutations

The individual criteria mutations (createScorecardCriterias, updateScorecardCriterias and deleteScorecardCriterias) are being deprecated and replaced with an expanded updateScorecard mutation which supports creating, updating and deleting criteria when updating a scorecard. The individual criteria mutations will be removed from the API on Aug 1, 2023.

More details

Why is this deprecation necessary?

This deprecation is necessary to improve scalability and enable future scorecard enhancements.

What is changing?

The three individual criteria mutations, createScorecardCriterias, updateScorecardCriterias, and deleteScorecardCriterias are being deprecated. Their functionality is now available as part of the updateScorecard mutation as createCriteria, updateCriteria, and deleteCriteria fields on UpdateCompassScorecardInput.

The following GraphQL types will be affected by this change:

CreateCompassScorecardCriteriasInput

UpdateCompassScorecardCriteriasInput

DeleteCompassScorecardCriteriasInput

UpdateCompassScorecardInput

Dates and rollout

The new createCriteria, updateCriteria, and deleteCriteria fields are available now on UpdateCompassScorecardInput. The createScorecardCriterias, updateScorecardCriterias, and deleteScorecardCriterias mutations, and their associated input types will be removed from the API on Aug 1, 2023.

Migration guidance

To migrate from the individual criteria mutations to the consolidated scorecard update mutation, follow these steps:

Update your createScorecardCriterias GraphQL mutations to use the updateScorecard mutation instead by populating the createCriteria field on the UpdateCompassScorecardInput with the same CreateCompassScorecardCriteriaInput currently used.

Update your updateScorecardCriterias GraphQL mutations to use the updateScorecard mutation instead by populating the updateCriteria field on the UpdateCompassScorecardInput with the same UpdateCompassScorecardCriteriaInput currently used.

Update your deleteScorecardCriterias GraphQL mutations to use the updateScorecard mutation instead by populating the deleteCriteria field on the UpdateCompassScorecardInput with the same DeleteCompassScorecardCriteriaInput currently used.

Note that criteria validations are run against the entire set of criteria when using the scorecardUpdate mutation. This means creating, updating, and deleting criteria must be combined into a single scorecardUpdate mutation call, or they may be rejected for failing validation.

Test your updated scorecardUpdate mutations with different combinations of the criteria inputs to ensure they each function as expected.

Once you have confirmed that your mutations work as expected, remove any references to the deprecated mutations.

Known issues

There are no known issues with the migration process. However, if you encounter any issues during the migration, please consult the Support section below.

Support

If you need help with the migration or have any questions, please visit the Compass Announcement category in CDAC or chat with our support engineers by clicking the “Give feedback” button in the top nav bar on your Compass site.

Q&A

As we receive questions from developers and partners about the deprecation, we will update this section with answers to common questions. Please refer to the Support section above if you have questions not addressed here.

21 April 2023

Deprecation Notice Deprecating componentType and componentTypeId fields of scorecard

In order to make Compass scorecard support multiple component types, we added a componentTypeIds field to our scorecard APIs. We are deprecating componentType and componentTypeId fields, and replace them with the new componentTypeIds field in following types: CompassScorecard, CreateCompassScorecardInput, UpdateCompassScorecardInput.

More details

Why is this deprecation necessary?

As we continue to grow and expand our component types, we need to provide greater flexibility in how our customers apply scorecards to their components. Currently, a scorecard can only be applied to one component type, with a limit of 50 scorecards. Customers have requested the ability to apply the same scorecard to multiple component types, reducing the burden of creating multiple identical scorecards to track components with different types.

What is changing?

To address this need and better support our growing component types, we are deprecating the componentType and componentTypeId fields in scorecard GraphQL APIs and replacing them with a new componentTypeIds field. The componentTypeIds field allows you to assign multiple component types to a single scorecard.

The following GraphQL types will be affected by this change:

  • CompassScorecard

  • CreateCompassScorecardInput

  • UpdateCompassScorecardInput

Dates and rollout

The new componentTypeIds field is now available. The componentType and componentTypeId fields will be removed from the API on Oct 20, 2023 (until then, they will continue to be supported).

Migration guidance

To migrate to the new componentTypeIds field, follow these steps:

  1. Update your GraphQL queries and mutations for Compass Scorecard to use the componentTypeIds field instead of the componentType and componentTypeId fields. The componentTypeIds field expects an array of component type IDs.

  2. Test your updated queries and mutations to ensure they work as expected with the new field.

  3. Once you have confirmed that your queries and mutations work with the new field, remove any references to the deprecated componentType and componentTypeId fields from your code.

Known issues

There are no known issues with the migration process. However, if you encounter any issues during the migration, please consult the Support section below.

Support

If you need help with the migration or have any questions, please visit the Compass Announcement category in CDAC or chat with our support engineers by clicking the “Give feedback” button in the top nav bar on your Compass site.

Q&A

As we receive questions from developers and partners about the deprecation, we will update this section with answers to common questions. Please refer to the Support section above if you have any questions that are not addressed here.

18 April 2023

Announcement Forge UI Kit `Image` component will have its source checked for permission

The src property of the UI Kit Image component will go through a permission check in the near future.

A specific date cannot be given for this change since it will depend on when each product adopts it.

More details

If the Image component is using an URL as its source, follow this External Permissions - Image guide to add permissions for that URL.

data:image URIs will be allowed by default as the Image source.

If the corresponding permission is not given to the source of the image when specified with a URL, then the image will not load.

4 April 2023

Added Grouping metrics by functions in developer console

To help you debug your Forge apps, the developer console now lets you group your metrics by app function. Each chart now has a Group by dropdown menu, with the option to select Function. For more information, see Monitor your apps.

3 April 2023

Announcement Function invocation time metrics for Forge apps in developer console

We’ve introduced a new metric to the developer console - invocation time! You can now see the invocation time for your Forge apps by selecting Metrics in the left menu and scrolling to the new invocation time chart, which shows the speed of your function invocations, separated into time buckets.

You can also select the Go to detailed view link at the bottom of the chart, to get a more in-depth view of invocation time, including the P50, P90, and P95 for individual functions.

30 March 2023

Deprecation Notice Jira issue glance module in Forge or Connect app being deprecated and replaced.

The jiraIssueGlances and jira:issueGlance module in Forge and Connect are being deprecated and replaced with the issueContext module on Oct 6, 2023.

30 January 2023

Added New installation links can now be generated in the developer console

To make it easier and safer to distribute your Forge app via the developer console, you can now generate new installation links. When you generate a new link, users with the previous link will no longer be able to install your app (however, they can still update to new versions). This gives you more control when distributing your app to specific audiences.

16 December 2022

Added App alerts now support custom target value

In the developer console, you can now edit the target value of your Forge app alert. Previously, the alert was set at a target value of 99%. Now you can choose from a number of values between 99% and 60%.
For more information, see Manage app alerts.

11 November 2022

Announcement Single value metrics in developer console

To quickly identify the current state of your Forge apps, the developer console now displays values, as well as charts, for each metric. For more information, see View app metrics.

2 November 2022

Announcement Grouping metrics by app version in developer console

To help you debug your Forge apps, the developer console now lets you group your metrics by app version. Each chart now has a Group by dropdown menu, with the option to select Version. For more information, see Monitor your apps.

Rate this page: