> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 2024

> New features, improvements, and fixes released in Cortex in 2024

Updates released in Cortex in 2024, newest first.

**December 17, 2024**

**Scorecard rules and CQL**

* You can now write Scorecard rules for SonarQube issues using `sonarqube.issues()`. Learn more about using this and the available filters in the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=SonarQube\&path=Issues).

**Improvements** 📈

* We’ve added [API support for Workflows](https://docs.cortex.io/docs/api/list-workflows). You can now easily retrieve workflow configurations programmatically, as well as create, list, update, and delete workflows within your Cortex instance.
* There is now an implicit join after branch actions in Workflows, letting you reuse a common path of actions afterward. This makes building workflows more efficient and simplifies the configuration experience. View the documentation here.
* We’ve added cross-account access support for New Relic! To set it up, add your New Relic configuration that supports subordinate accounts & enable the cross-account access feature. Learn more in [our docs](https://docs.cortex.io/docs/reference/integrations/newrelic.md#cross-account-access).
* Custom metric changes through the API are now included in audit logs.

**December 10, 2024**

**Team member roles:** You can now sync team member roles from integrations like Workday. To enable this, head over to the [Team entities settings page](https://app.getcortexapp.com/admin/settings/team-entities?activeTab=Roles) and enable importing roles from integrations in the roles tab.

**Scorecard rules and CQL**

* We now support using `git.topLanguage` for Azure DevOps. In order to pull this, Cortex requires “Analytics: `read`” permission.
* We’ve added support for verifying a repos branch protection in CQL for Bitbucket using `git.branchProtection`. Take a look at examples in our [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=Bitbucket\&path=Branch%20protection%20details) and learn more about required permissions in the docs.

**Improvements** 📈

* We’ve added support for a secrets input type for user input actions in Workflows. With the secrets input, you can obfuscate sensitive values like passwords using the **Secret** option on the input type selector. Learn more in [our docs](https://docs.cortex.io/docs/walkthroughs/deep-dives/cortex-tools/workflows#step-3-add-actions-to-your-workflow).
* You can now quickly duplicate steps on the Workflows canvas by clicking the overflow menu on the right side of an action and then “Duplicate action”.
* We’ve added support for importing Apigee resources from Google Cloud. Learn more about the required permissions in [our docs](https://docs.cortex.io/docs/reference/integrations/google).
* If you’re using Azure DevOps, you’ll now see the top language for an entity with repository information in the overview page. In order to pull this, Cortex requires “Analytics: `read`” permission.
* Custom event & dependency changes through the API are now included in audit logs.
* We’ve decoupled Scaffolder permissions to allow users with exclusively the ‘Execute Scaffolder’ role to run Scaffolders.
* Users can now subscribe (and unsubscribe) from Workflows-related [notifications](https://app.getcortexapp.com/admin/settings/notifications) in [Preferences > Notifications subscriptions](https://app.getcortexapp.com/admin/settings/notification-subscriptions). You can also manage workspace notifications in [Preferences > Notifications](https://app.getcortexapp.com/admin/settings/notifications).

**Bug fixes** 🐛

* We made a fix to prevent entities from dropping to a “no level” state in the interim between updating or adding a level rule and evaluating it for entities. Now, the entity will remain in the previous state until the rules have been reevaluated.
* We fixed a bug within Initiative reporting to treat partially failing entities as failing. Before, if the entity had some failing and some passing, it would show up for both.
* We’ve updated how we handle incidents from PagerDuty to prevent duplicate notifications from being sent for [On-call Assistant](https://docs.cortex.io/docs/walkthroughs/deep-dives/integrations/oncall-assistant.md).
* We fixed an issue with roleTags not saving for users through the API.
* We’ve improved performance and reliability of our AWS GitOps processing.

**December 4, 2024**

**Plugins marketplace**

Today we’re excited to share the launch of Cortex’s new [Plugin Marketplace](https://app.getcortexapp.com/admin/plugins?activeTab=Marketplace). In the Plugins page, you’ll now have a marketplace tab. Each plugin in the marketplace comes complete with docs and install instructions. To install a plugin, you must have permission to “Edit plugins”.

We have a few plugins, both with existing integrations (like ServiceNow and Pagerduty), and new ones (like CloudForecast). Cortex will continue adding new plugins to this Marketplace, and will continue working with customers and partners to test and validate plugins that are ready to be shared!

To learn more, check out the blog authored by the Cortex Solutions Architect that spearheaded this project! Full documentation on the marketplace and each plugin is available in [Git](https://github.com/cortexapps/cortex-plugins), and documentation on creating a plugin is in our [docs](https://docs.cortex.io/docs/walkthroughs/deep-dives/plugins/creating-plugins).

**December 3, 2024**

**Actions are now Workflows:** All of your actions are now one- or two-step [Workflows](https://app.getcortexapp.com/admin/workflows). We’ll be keeping the Actions tab around for 30 days. Here, you’ll be able to see the list of Actions & access past history but you’ll have to run any existing Actions from their equivalent workflow.

**Improvements** 📈

* We’ve decoupled the permissions for running the Scaffolder from the permission to “Configure Catalog”. If you have “Team Ownership Entity Editing” enabled, you can encourage users to use the Scaffolder when creating new entities. If you’d like to require certain inputs, such as requiring ownership, as part of running the Scaffolder, you can set up a Workflow to do so.
* Adding actions has been moved into a modal within Workflows. This change enables you to focus on configuring actions in the right panel on the Workflows canvas.

**Bug fixes** 🐛

* We’ve fixed an issue with importing Amazon ECS task definitions.
* We’ve improved performance on the Entity Overview page.
* Custom entities now support properties with null types.

**November 26, 2024**

**Improvements** 📈

* We deprecated the `timestamp` query parameter in the [List custom events API](https://docs.cortex.io/docs/api/list-custom-events-for-entity) in favor of `startTime` and `endTime` params.
* We’ve added validation when creating a custom metric using CQL to ensure that the expression returns a number.

**Bug fixes** 🐛

* We’ve fixed an issue where the CQL report was flickering on scroll
* We’ve fixed a bug with Scorecards rule filtering not working properly.
* We’ve fixed an issue for customers using GitOps for Scorecards.

**November 25, 2024**

**Actions Migration**

**On December 2nd, Actions will be migrated to Workflows.** All existing actions will become one or two step [Workflows](https://app.getcortexapp.com/admin/workflows). We’ll be keeping the Actions tab around for 30 days. You’ll be able to see the list of Actions & access past history but you’ll have to run any existing Actions from their equivalent workflow.

**November 19, 2024**

**Notification logs:** Similar to the existing Audit & GitOps logs pages, we’ve added a new [notification logs page](https://app.getcortexapp.com/admin/settings/notification-logs) to give you visibility into the notification system in Cortex. You can now see the list of all notifications sent alongside their status & corresponding errors if it failed to deliver. When you click on a notification, you can see the list of its recipients and the notification content. Learn more about notification logs in [our docs](https://docs.cortex.io/docs/walkthroughs/workspace-settings/notification-logs.md).

**Improvements** 📈

* We’ve added new Scorecard templates, including ones for Production Readiness and Vulnerability Management.
* We’ve added new Workflow templates, including ones for creating a service, team, and domain in Cortex as well as retrieving entity details or deleting an entity.
* You can now override pre-populated text values for user input actions in Workflows during a run.
* Running workflows is no longer dependent on having the “View Workflow Runs” permission enabled.
* We’ve updated the subject for Weekly Report emails to make it clear the team & dates that it applies to.

**Bug fixes** 🐛

* We’ve fixed an issue where Jira issues were not loading on the Developer Homepage.
* We’ve fixed an issue with identity mappings for the Slack integration.
* We fixed an issue detecting packages when the default branch is not master.

**Jira in Eng Intel**

🚀 **New Feature Release: Jira Metrics in Engineering Intelligence**

We’re excited to announce the addition of **5 new Jira metrics** to Engineering Intelligence! Now, you can integrate Jira data, enabling a holistic view of your engineering efforts.

With this update, you can analyze **delivery timelines and time allocation** alongside your existing Git-related metrics, giving you a unified platform to better understand your team’s productivity and delivery efficiency.

This powerful combination empowers you to identify trends, balance priorities, and make data-driven decisions with ease. Learn more about Jira metrics in Engineering Intelligence today [here](https://docs.cortex.io/docs/walkthroughs/deep-dives/eng-intelligence/jira-metrics)!

**November 13, 2024**

**Scorecard rules and CQL**

* All teams have it least one member using `entity.members().length > 0`
* Each team has at least one member in the team with the “Manager” role using `entity.members().filter((member) => member.roles.filter((role) => role.tag == "manager").length > 0).length > 0`

Learn more in the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Team%20metadata\&path=Members).

* We’ve added tags to our [SLOs object](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=SLOs) in CQL.

**Improvements** 📈

* You can now import teams from Azure DevOps into the teams catalog. To do so, go to import teams, select Azure DevOps as the identity provider, & select the discovered teams you’d like to import.
* In addition to GitHub, we’ve added more identity mappings to the Workflows user context, so you can easily add and access user account info (username or account ID) in your workflow. The following mappings are now available:
  * `azure_devops`
  * `bitbucket`
  * `clickup`
  * `github`
  * `gitlab`
  * `jira`
  * `microsoft_teams`
  * `opsgenie`
  * `pagerduty`
  * `service_now`
  * `slack`

**November 5, 2024**

**Score drop notification for Scorecards:** We’ve added a new notification type for Scorecards that will notify the entity or team channel for an entity whenever the entity’s score drops after it’s evaluated. This can be configured for each individual Scorecard in the edit page or in the [Scorecard YAML](https://docs.cortex.io/docs/reference/basics/scorecards#descriptor). Learn more about creating and editing Scorecards in [our docs](https://docs.cortex.io/docs/walkthroughs/getting-started/scorecards).

**Improvements** 📈

* We’ve added source information for team members when using the [entities API](https://docs.cortex.io/docs/api/list-all-entities). This brings our entities API to parity with the existing teams API.
* Team member roles will now be displayed in the owners page for entities.
* You can now assign multiple team member roles to a team member.
* If you’re using “team ownership entity editing”, you can now give edit access to all team members in the [Settings page](https://app.getcortexapp.com/admin/settings/entities?activeTab=Teams). When enabled, you will not be able to turn off edit access for individual members in your teams configuration when this is enabled. Learn more about setting up team-based ownership editing in [our docs](https://docs.cortex.io/docs/walkthroughs/workspace-settings/team-entity-editing.md).
* We’ve removed the limit on the number of nested Conditional Branch Actions a workflow can contain to support more complex operations.
* We’ve added a Copy button to each workflow on the main Workflows list to make bootstrapping new workflows easier.
* We’ve added a user’s GitHub handle to the user context available to actions during a Workflow run.
* We’ve added the CQL expression to the Related Activity tab for CQL Custom Metrics

**Bug fixes** 🐛

* We’ve fixed a bug that could cause copying an old Scorecard to create a copy with incorrect filters
* We’ve removed all archived entities from notifications
* We’ve fixed a bug that caused Jira issues to not be reflected on the home page
* We’ve fixed a bug that caused the OR operator to not work correctly when using semverRange

**October 29, 2024**

**Scorecard rules and CQL**

* We’ve added urgency information to the incident object in `oncall.incidents()` . Take a look at examples in the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=PagerDuty\&path=Incidents).

**Improvements** 📈

* We’ve created a separate permissions to “Configure Identity mappings”. Users with this permission can review how team members defined in the team catalog are matched to external accounts (e.g. GitHub, Jira, PagerDuty, or Slack)

**Bug fixes** 🐛

* We’ve fixed a bug that caused duplicate Jira tickets to display on the Dev Homepage when they are assigned to another project
* We’ve fixed a bug that caused team scoped plugins to not show up under team in appearance settings.

**October 28, 2024**

**Workflows GA & permissions enhancements**

We’ve added more granular control over which users are authorized to view, edit, and run individual workflows, providing more control over sensitive operations.

With this latest release, we are also pleased to announce Workflows is now GA and this powerful feature is now available to all qualifying customers. Use Workflows to automate actions across multiple tools to speed service creation, user onboarding, incident response, resource provisioning, and much more. Take a look at our[ docs](https://docs.cortex.io/docs/walkthroughs/deep-dives/cortex-tools/workflows) to get started with Workflows!

*If you don’t have Workflows enabled and would like to learn more, please reach out to your customer success manager.*

**October 22, 2024**

**Syncing ownership tags from Azure Resources:** Keeping entity YAMLs and ownership information can be tedious if resources are updated frequently. To alleviate some of that upkeep, the Azure Resources integration can now bring in Azure Resources tags into Cortex. This will help keep entities in Cortex up to date with the latest ownership information inherited from Azure Resources. To enable this feature, enable the “Sync ownership from Azure” toggle in the teams tab of the [Azure Resources Settings page](https://app.getcortexapp.com/admin/settings/azureresources).

**Entity verification admin view:** In the Settings page for [entity verification](https://docs.cortex.io/docs/walkthroughs/workspace-settings/entity-verification.md), you can now click on an entity verification period to view details about which entities have been verified & by whom.

**Improvements** 📈

* We’ve added support for importing Artifact Registry & VPC Serverless Connector resources from Google Cloud. Learn more about the required permissions in [our docs](https://docs.cortex.io/docs/reference/integrations/google).

**Bug fixes** 🐛

* We’ve fixed a broken link to Scorecard Rule Examples on the Edit Scorecard Rules page.
* We increased the level of mathematical precision used when evaluating CQL queries to address issues where rounding could cause incorrect comparison results.
* We’ve fixed a bug that could cause Snyk code projects to show no priority score, even though there is a score visible in the Snyk UI.

**October 15, 2024**

**Azure DevOps multi-instance support:** If your organization has multiple instances of Azure DevOps, you can now configure all of them in the Settings page. This will allow you to discover and import services from all repositories across all configured Azure DevOps accounts. Read more about configuring Azure DevOps in [our docs](https://docs.cortex.io/docs/reference/integrations/azuredevops.md).

[**Entity verification**](https://docs.cortex.io/docs/walkthroughs/workspace-settings/entity-verification.md) **improvements:** We’ve improved the list of entity verification periods by indicating clearly which periods are expired and sorting by period start and end date. We’ve also added the ability to require adding a reason for making an entity Invalid as part of the verification process.

**Scorecard rules and CQL**

* If you’re using Eng Intelligence, you’ll now be able to define Scorecard rules for custom metrics. Take a look at the CQL explorer to see examples on using `customMetrics()`.

**Improvements** 📈

* You can now define dependency tags for Azure Resources to automatically map dependencies between entities. Learn more about setting automatic dependency mapping from Azure Resources in [our docs](https://docs.cortex.io/docs/reference/integrations/azureresources.md#define-a-dependency).
* You can now use custom data in CQL based custom metrics in Engineering Intelligence as long as it returns a number.
* We’ve added support for importing Spanner resources from Google Cloud. Learn more about the required permissions in [our docs](https://docs.cortex.io/docs/reference/integrations/google).
* You can now use custom roles when setting a minimum role for plugins. The plugin will be visible to any users with that custom role or any user that has all the permissions that the custom role grants. Read more about creating plugins in our docs.
* We’ve improved the performance of the unowned entity modal in the Executive Report in the case where many entities do not have owners.

**Bug fixes** 🐛

* We fixed a bug in the Workflows Cortex Entity input which incorrectly presented an empty list for Teams and Domains.
* We’ve fixed a bug where the Developer Homepage was only showing PRs from only one provider even if you had multiple configured.
* We’ve fixed a bug that could result in some GitHub review requests not showing on the Developer Homepage, in the case where Cortex and GitHub email addresses don’t match.
* We’ve fixed a bug which caused an error when attempting to edit an Entity Verification period if a user role used in that period had been deleted.
* We’ve fixed a bug which prevented an administrator from saving changes to an existing Entity Verification period if the start date was unchanged.
* We’ve fixed the tooltip shown when hovering over a failed Scorecard rule with a complex expression to be more helpful.

**October 14, 2024**

**Workflows permission changes**

**Workflows permission changes:** As part of the permission improvements we are currently making in Workflows, there are a few changes to be aware of that will affect who can view and edit your workflows:

* We are adding a **View Workflows** permission that will automatically be added to the standard User, Manager, and Admin roles, and can be manually added to any custom roles you might be using. Any users without this permission, including those with the standard Viewer role, will not be able to see or interact with any workflows.
* The **Edit Workflows** permission will be included in the Manager and Admin roles. Note that the Manager role did not previously have permission to edit workflows. If you have users with the Manager role who you do not wish to have workflow editing permission, you can switch them to another standard role or a custom role without the Edit Workflows permission to preserve that experience.
* We will remove the Permission selector within each workflow. Viewing and editing workflows will be entirely controlled by the two granular permissions mentioned above.

**Please note: We will be releasing these changes on Monday, October 21st**. Please reach out to your Customer Success Manager if you have any questions or concerns.

**October 8, 2024**

**Improvements** 📈

* Notifications to entity Slack channels will be disabled by default to avoid noise.
* We’ve added markdown support for Entity Verification period descriptions.
* We’ve improved the flow for verifying entities to streamline the process & require less clicks.
* We’ve added support for importing Composer GCP Type resources from Google Cloud. Learn more about the required permissions in [our docs](https://docs.cortex.io/docs/reference/integrations/google).

**Bug fixes** 🐛

* We’ve fixed an issue with an invalid formula in the predefined Circle CI “Check if Circle CI project is set” rule
* We’ve fixed a bug related to sending too many entity verification notifications based on the filters.
* We’ve fixed a bug with ClickUp identity mappings

**October 1, 2024**

**Entity Slack Channel Notifications:** We’ve added the ability to send notifications the the slack channel associated with an entity, rather than the owning team or users. These preferences can be controlled in the Workspace notifications subscriptions section of the Settings → Notifications page.

**Custom Metrics:** Custom metrics are now viewable on Entity pages.

**Improvements** 📈

* We’ve added the following new granular permissions:
* Configure Plugin appearance - users with this permission can change plugin appearance settings
* Edit Create API keys - users with this permission can create API keys
* View Breaking API changes - users with this permission can access the Breaking API changes page
* Archive Entities - users with this permission can archive entities
* Edit Entities - users with this permission can edit entities
* View Initiatives - users with this permission can view Initiatives
* Configure Discovery audit events - users with this permission can manage events in Discovery Audit Log
* Configure Integrations - users with this permission can manage integrations configuration
* Enable Relationship graph - users with this permission can access the Relationship graph
* We’ve moved Entity Verification Period setup to its own page under Settings → Entity verification, and added more details about each verification period to the table shown there, including a count of entities verified to-date.
* We’ve added an improved loader to several large report pages to make it clearer that data is being processed.
* We’ve improved error handling in the Workflows HTTP Action to give the user more information about why a particular request is failing.
* We’ve added a confirmation modal while deleting a custom role

**Bug fixes** 🐛

* We fixed a bug which would cause an entity search to sometimes fail to return results for uppercase and wildcard searches.
* We fixed a bug which would sometimes result in a Teams search for an individual’s name to not return teams which that person is a member of.
* We’ve fixed a bug which caused sorting issues in the list of traces for Eng Intelligence Custom Metrics.
* We’ve fixed a bug with a recently upgraded version of the iframe-resizer component that caused visibility issues with some plugins due to a bad iframe height.
* We’ve fixed a bug which briefly caused errors when importing teams with parents and/or children.
* We’ve fixed a bug in the Scaffolder that would sometimes show an error for a valid GitLab project selection.
* We’ve fixed a bug in the import flow that prevented a user from manually importing an entity with a built-in type.

**September 24, 2024**

**Custom Metrics for Eng Intelligence:** If you’re using Eng Intelligence, you can now create your own metrics through the public API and CQL, giving you the ability to bring in any information you’d like into the Eng Intelligence view.

**Cortex ID for entities:** In addition to the x-cortex-tag as an entity identifier, we’ve created the concept of a Cortex ID. There are many cases in which this kind of ID is helpful, but the most common use case is when you need an entity ID that is unique and immutable for historical tracking and reporting outside of Cortex. The ID format is 18 characters in length and is available in the external API, CQL, and in-app. It will apply to any entity (teams, domains, services, resources, etc.) created previously and in the future, regardless of how it is created (workflows, in app, sync). As part of this change, entity URLs have been updated to use the Cortex ID. Existing URLs will redirect to the new URLs.

**Scorecard rules and CQL**

* We’ve improved error handling around queries like git.numOfVulnerabilities(severity=\["INVALID"]) so that a useful error message is returned instead of simply 0 for invalid severity strings.

**Improvements** 📈

* We’ve added the following new granular permissions:
* Delete Entities - users with this permission can delete entities
* Edit Entity types - users with this permission can create, update, and delete entity type definitions
* Configure Workspace Notifications Settings - users with this permission can access and update workspace notifications settings
* Edit Catalogs - users with this permission can create, update, and delete catalog pages
* View Roles - users with this permission can view roles defined in the system
* Configure Roles - users with this permission can create, update, and delete roles defined in the system
* Edit Initiatives - users with this permission can create, update, and delete initiatives
* We improved the performance of PagerDuty incident fetching.
* We’ve added a new configuration option to the auto-archival process. Right now auto-archival can be integration- or GitOps-based.

**Bug fixes** 🐛

* We’ve fixed the validation on Workflow Action slugs to be consistent with that of Workflow slugs.
* We fixed a bug which prevented filtering entities by Team on a Scorecard.
* We’ve fixed a UI issue that caused tooltip flickering when hovering over a progress report graph.
* We’ve fixed a bug in our Wiz integration which resulted in the wrong icon being displayed next to Wiz issues.
* We’ve fixed an issue that was preventing Scorecard rule exemptions from being created for a short period of time.
* We fixed a bug which could cause an inconsistent number of entities to be included in Bird’s Eye and All Scorecards reports when grouped by team.
* We’ve fixed a bug related to GitOps per-type settings. Custom entity settings were overridden by Options by entity types.
* We’ve fixed a bug with missing team cardinality for workflows and identity mapping team filters.

**September 17, 2024**

**Empty teams:** You’ll now see teams without members in all existing flows, including the owners information for entities, all dropdowns & filters, and the public API.

**Domains from ServiceNow:** We’ve added support for importing domains and domain relationships from ServiceNow. Right now, users can configure mappings, sync and import domains either manually or automatically.

**Scorecard rules and CQL**

* We’ve added a new gitHub rule called `git.matchingFiles(fileName)` that takes a regex and will return a list of files in the repository that match that regular expression, allowing for more efficient searching for specific filenames.
* Team name can now be queried in CQL Reports.

**Improvements** 📈

* We’ve added new permission to control view access to the Scorecard’s exemptions. Only users with this permission will be able to see the list of exemptions related to Scorecards.
* A new setting has been added to the Settings → Integrations → GitHub page to opt out of GitHub issues support if GitHub issues aren’t relevant for your organization.
* Descriptions for links are now returned from the public catalog API.
* For Azure DevOps, assigned reviews for the team a user is a part of are now visible in the Assigned Reviews tab of the Dev Homepage.
* We’ve updated the Entity Verification feature to show a different badge on the entity page for entities that have been verified correct and incorrect (based on the most recent verification period).

**Bug fixes** 🐛

* We’ve fixed an issue in the Workflows Cortex Entity input which resulted in archived entities being shown when displaying as a hierarchy.
* We’ve fixed a display issue on the CQL Report page that could cause the report to load very slowly or become unresponsive.
* We’ve updated handling of Workflow and Workflow Action slugs to enforce that they can’t differ only in case, which might lead to confusion.
* The repository section will no longer be shown for services that are imported from Azure Devops, as it is not supported.
* We’ve fixed a bug which prevented editing a field of a verification period with a start date earlier than the current date.
* We’ve made significant performance improvements to the Teams Catalog page for customers with a very large number of teams.
* We’ve fixed a spacing issue on the ClickUp page of an entity to make the table more readable.

**September 10, 2024**

**Workflows template library:** Workflows can now be created from a variety of pre-defined templates to make getting started with common use cases easier.

*If you don’t have Workflows enabled, please reach out to your customer success manager.*

**"Hide team with 0 members” toggle removed:** As part of our work to remove special treatment for empty teams, we’ve removed the “Hide team with 0 members” toggle in the teams catalog page.

**Scorecard rules and CQL**

* We’ve updated the `snyk.numberOfIssues` CQL expression to be inclusive of all Snyk issue types. The existing implementation is hitting a legacy endpoint that does not include issues from code projects or configuration issues. This update brings `snyk.numberOfIssues()` in line with the implementation of `snyk.issues()` in order to provide a consistent experience. If you wish to remain consistent with the previous implementation of `snyk.numberOfIssues`, you can update the CQL expression to `snyk.numOfIssues(types=["Lisence", "Vuln"])`
* We’ve added CQL support for `packageVersionRange()` and `isPackageVersionRange()` to improve our support for semantic versioning of packages.

**Bug fixes** 🐛

* We fixed an issue that caused a blank screen to appear when attempting to configure some entities
* We fixed a bug which caused global workflows to appear on the Workflows tab for a specific entity. Only entity-scoped workflows will appear there.
* We’ve fixed a bug that prevented an Entity Verification Period from being edited if it referenced a Team Member Role that has been deleted
* We’ve fixed a bug in CQL that resulted in incorrect “only maps with strings keys are currently supported” message
* We’ve fixed a bug with Cortex linter related to invalid files filtering
* Discovered BambooHR teams will now be surfaced during the import teams flow

**September 4, 2024**

**Azure DevOps Work Items integration:** We’re enhanced our existing Azure DevOps integration to support work items. If you’re using work items, you can now see any assigned to you in the developer homepage and associate work items with entities. We also support creating work items from active initiatives, similar to how Jira works today. Learn more about the integration in [our docs](https://docs.cortex.io/docs/reference/integrations/azuredevops.md).

**x-cortex-parents Migration**: If you have GitOps disabled for entity types, we have migrated entity YAMLs on Tuesday, September 3rd between 4 - 6 pm PST. You should not see any impact to your entities & their hierarchy but please reach out to our support team if you do.

**We are deprecating the `x-cortex-domain-parents` descriptor in the entity YAML on October 31st.** All existing functionality can be found using `x-cortex-parents` as shown in [our docs](https://docs.cortex.io/docs/reference/basics/entities#example-cortexyaml-1).

If you have GitOps disabled for entity types, we will automatically be migrating entity YAMLs on Tuesday, September 3rd between 4 - 6 pm PST. You should not see any impact to your entities & their hierarchy but please reach out to our support team if you do.

For entity types with GitOps enabled, you will need to migrate any existing entity YAMLs by October 31st. Failure to do so will result in hierarchy errors in entity pages as well as reporting functionality.

**Public API permissions:** We’ve updated permissions of the following public API endpoints:

* [Retrieve audit logs](https://docs.cortex.io/docs/api/get-audit-logs) requires “View audit logs” permission
* [Retrieve GitOps logs](https://docs.cortex.io/docs/api/list-git-ops-logs) requires “View GitOps logs” permission
* [Retrieve allowlist ](https://docs.cortex.io/docs/api/list-allowed-ip-addresses)requires “Configure IP allowlist” permission
* [Update allowlist](https://docs.cortex.io/docs/api/upsert-allowed-ip-addresses) requires “Configure IP allowlist” permission
* [Validate allowlist ](https://docs.cortex.io/docs/api/validate-allowed-ip-addresses)requires “Configure IP allowlist” permission
* [SCIM: Find users](https://docs.cortex.io/docs/api/get-user) requires “Open ID Connector & SCIM” permission
* [SCIM: Create user](https://docs.cortex.io/docs/api/create-user) requires “Open ID Connector & SCIM” permission
* [SCIM: Update user](https://docs.cortex.io/docs/api/update-user) requires “Open ID Connector & SCIM” permission
* [SCIM: Patch user](https://docs.cortex.io/docs/api/patch-user) requires “Open ID Connector & SCIM” permission
* [SCIM: Delete user](https://docs.cortex.io/docs/api/delete-user) requires “Open ID Connector & SCIM” permission

**Scorecard rules and CQL**

* We’ve added sku & template details to the `azureResource.details()` object in CQL.

**Improvements** 📈

* We’ve updated our tab names to include the object name & make it easier to distinguish between multiple open tabs. For example, you’ll now see “Service | Brain App” and “Scorecard | Production Readiness” as the tab names.
* If a Scorecard contains entities that do not have any rules applied to them due to the filter configuration for rules, the entities will be at “No Level”. When looking at corresponding stats for that entity, the percentile & rank is displayed as “N/A”.
* Workflows that are scoped to run for particular entities are now available to execute directly from the entity detail page for those entities, under the Workflows tab.
* You can now search for entities based on their AWS details. We’ve added the following AWS attributes to the index: For example, you can now search for entities of category EC2 in the any of us-west regions with the query: **aws-type:"AWS::EC2" AND aws-region:"us-west".**
  * **aws-account-id** - account id number
  * **aws-account-name** - account alias
  * **aws-region** - AWS region of the resource
  * **aws-type** - AWS type of the resource
  * **aws-name** - AWS identifier of the resource
* If you’re using the Google Cloud integration, you can now import instance groups. To get started, simply update the [permissions](https://docs.cortex.io/docs/reference/integrations/google#setup) for your configured service account. You’ll be able to see newly discovered resources after syncing the discovered entities. If you have auto import enabled for resources, these will be pulled in after permissions have been updated during the next sync.

**Bug fixes** 🐛

* We’ve fixed a bug with viewing historical data when grouping by domains in Eng Intelligence.
* We fixed a bug in the import flow for GitHub repositories which resulted in other service types also being imported when Select All was checked.
* We’ve fixed case-insensitive searching in the Workflows Cortex Entity input when “Display As Hierarchy” option is selected.

**September 3, 2024**

**snyk.numberOfIssues update**

On Tuesday, September 10th at 9 am PST, we will be updating the `snyk.numberOfIssues` CQL expression to be inclusive of all Snyk issue types. The existing implementation is hitting a legacy endpoint that does not include issues from code projects or configuration issues. The update will bring `snyk.numberOfIssues()` in line with the implementation of `snyk.issues()` in order to provide a consistent experience.

If you wish to remain consistent with today’s implementation of `snyk.numberOfIssues`, you can update the CQL expression to `snyk.numOfIssues(types=["Lisence", "Vuln"])` prior to Tuesday, September 10th.

**August 27, 2024**

**Developer homepage pull requests:** We’ve updated the developer homepage to only show pull requests associated with GitHub organizations configured in Cortex. Users who have open pull requests outside of their organization (e.g. open source related pull requests) will no longer see these in the developer homepage.

Additionally, you can no longer see pull requests that are over 2 years old.

**"Hide team with 0 members” toggle default:** As part of our work to remove special treatment for empty teams, we’ve updated the default of the “Hide team with 0 members” toggle in the teams catalog page to be false.

**Improvements** 📈

* We’ve added the entity type to the search index in the catalog pages.
* If you’re using the Google Cloud integration, you can now import resources of types Vertex AI, App Engine service, and Kubernetes Engine. To get started, simply update the [permissions](https://docs.cortex.io/docs/reference/integrations/google#setup) for your configured service account. You’ll be able to see newly discovered resources after syncing the discovered entities. If you have auto import enabled for resources, these will be pulled in after permissions have been updated during the next sync.
* We’ve added additional information to the details object for Azure Resources, both in the entity page and CQL.
* We’ve added the workflow name to notification previews for Slack, Microsoft Teams, and email.
* We’ve updated our handling when creating Jira issues during the initaitive flow to use the specified issue configuration if the entity YAML has required fields that are not specified. This will not prevent all potential problems during the flow but significantly reduce them.

**Bug fixes** 🐛

* We’ve fixed a bug with the importing of resources from Azure Resources for entities with the same type & account information.
* We’ve fixed an issue with uploading images to customize the appearance of your workspace.

**August 26, 2024**

**x-cortex-domain-parents deprecation**

**We are deprecating the `x-cortex-domain-parents` descriptor in the entity YAML on October 31st.** All existing functionality can be found using `x-cortex-parents` as shown in [our docs](https://docs.cortex.io/docs/reference/basics/entities#example-cortexyaml-1).

If you have GitOps disabled for entity types, we will automatically be migrating entity YAMLs on Tuesday, September 3rd between 4 - 6 pm PST. You should not see any impact to your entities & their hierarchy but please reach out to our support team if you do.

For entity types with GitOps enabled, you will need to migrate any existing entity YAMLs by October 31st. Failure to do so will result in hierarchy errors in entity pages as well as reporting functionality.

Let us know if you have any questions.

**Public API permissions**

On Tuesday, September 3rd, we’ll be updating permissions of the following public API endpoints to require permissions to “Edit Settings”. If you’re using these endpoints, please make sure your API key has the correct permissions.

* [Retrieve audit logs](https://docs.cortex.io/docs/api/get-audit-logs)
* [Retrieve GitOps logs](https://docs.cortex.io/docs/api/list-git-ops-logs)
* [Retrieve allowlist ](https://docs.cortex.io/docs/api/list-allowed-ip-addresses)
* [Update allowlist](https://docs.cortex.io/docs/api/upsert-allowed-ip-addresses)
* [Validate allowlist ](https://docs.cortex.io/docs/api/validate-allowed-ip-addresses)
* [SCIM: Find users](https://docs.cortex.io/docs/api/get-user)
* [SCIM: Create user](https://docs.cortex.io/docs/api/create-user)
* [SCIM: Update user](https://docs.cortex.io/docs/api/update-user)
* [SCIM: Patch user](https://docs.cortex.io/docs/api/patch-user)
* [SCIM: Delete user](https://docs.cortex.io/docs/api/delete-user)

**August 20, 2024**

**Audit log retention:** Our 30-day audit log retention policy is now in place, effective August 19th. If you have any questions about this change, please contact your customer success manager.

**Conditional branching for Workflows:** If you have workflows enabled, you’ll see a new branch action which allows you to add conditional branches to your workflows. Our product documentation has been updated with details, and can be found [here](https://docs.cortex.io/docs/walkthroughs/deep-dives/cortex-tools/workflows). *If you don’t have Workflows enabled, please reach out to your customer success manager.*

**Improvements** 📈

* We added new GCP types related to Google BigQuery (Dataset with Routines and Connection).
* As part of our work to remove special treatment for empty teams, we’ve updated the Teams Catalog, Bird’s Eye report, and All Scorecards report to clearly indicate where teams have no members.
* We made significant performance improvements to the Teams catalog page when the catalog contains thousands of teams.

**Bug fixes** 🐛

* We fixed an issue where some users might not be mapped when multiple GitLab instances are configured.
* We’ve fixed a bug in CQL Query Builder that was incorrectly saving some queries.
* We updated the help text around entity tag to clarify that “/” and “:” are acceptable characters.
* We fixed an issue in our Opsgenie integration which could cause a 404 Not Found error to be displayed when applying an on-call rotation.
* We’ve fixed support for SVG images when updating the logo on the Appearance page.
* We fixed hierarchy support on the Bird’s Eye report for Scorecards that only apply to teams.
* We fixed an inability to add children to Teams when UI edit is disabled by default for new entity types.
* We’ve fixed an issue with our GitHub Dependabot integration which prevented some vulnerabilities from being downloaded.
* In Eng Intelligence, we’ve filtered out self-reviews from the “Avg PRs reviewed/week” metric.
* We fixed a UI issue which caused the column headers from the Bird’s Eye report to cover some left navigation menu items.

**August 13, 2024**

**Audit log retention:** We've updated our retention policy for audit logs to 30 days. If you would like a longer retention period, please contact your customer success manager by Monday, August 19th.

**Improvements** 📈

* If you’re using the Google Cloud integration, you can now import resources of type Cloud Run. To get started, simply update the [permissions](https://docs.cortex.io/docs/reference/integrations/google#setup) for your configured service account. You’ll be able to see newly discovered resources after syncing the discovered entities. If you have auto import enabled for resources, these will be pulled in after permissions have been updated during the next sync.
* We’ve alphabetized the repository selection input in the scaffolder action to make finding the correct repo easier.

**Bug fixes** 🐛

* When attempting to delete a team, we’ve clarified the UI when that team cannot be deleted because it owns entities, and suggest archiving that team instead.
* We’ve fixed some inconsistent Scorecard grouping by team when ownership is inherited via a domain.
* We’ve fixed the entity verification flow to allow authorized users within a team to verify that team entity.
* We’ve fixed issue with missing SLO values in the NewRelic integration
* The dependencies tab now shows valid icons for AWS resources
* We’ve fixed a bug with importing Azure resources that resulted in not being able to see all available resources.
* We’ve fixed a few bugs with basepath support in the Bitbucket integration
* We’ve fixed our error handling in the Veracode integration that could’ve resulted in some data not getting properly retrieved.

**August 7, 2024**

**Upcoming change to developer homepage pull requests**

On August 19th, we’ll be updating the developer homepage to only show pull requests associated with GitHub organizations configured in Cortex. Users who have open pull requests outside of their organization (e.g. open source related pull requests) will no longer see these in the developer homepage.

Additionally, you will no longer see pull requests that are over 2 years old.

**August 6, 2024**

**GitOps by type support:** We’ve added granularity to GitOps settings for each type. You can now specify whether entities of a type have GitOps enabled, can be imported through the UI, and its repository allowlist. As part of this change, you can also specify whether you want to auto archive entities of that type. This gives a lot more flexibility for custom entity types.

**Scorecard rules and CQL**

* We’ve added `jira.issues` and `jira.rawJql` to CQL. The difference between the two is that `rawJql` is not tied to the entity YAML by default. Both return a list of issues, allowing you to filter as needed when writing Scorecard rules. Take a look at the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer) to see examples.
* We’ve extended support of existing git CQL expressions to Azure DevOps, including checking for branches, branch protection, and commits. You can see the full list in the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer).

**Improvements** 📈

* We’ve overhauled our search index and weighting system to ensure better sorted search results. We’ve removed dependencies, children, and parent tags from the search index as this has caused confusion for many users.
* If you’re using the Google Cloud integration, you can now import resources of type memorystore and compute engine. To get started, simply update the [permissions](https://docs.cortex.io/docs/reference/integrations/google#setup) for your configured service account. You’ll be able to see newly discovered resources after syncing the discovered entities. If you have auto import enabled for resources, these will be pulled in after permissions have been updated during the next sync.
* You can now set the default & minimum evaluation windows for Scorecards for your workspace in the [Scorecards settings page](https://app.getcortexapp.com/admin/settings/scorecards). By default, Cortex evaluates Scorecards every 4 hours. This setting gives you the ability to control Scorecards created by other users with permission to create and edit Scorecards and prevent someone from potentially causing issues through over-evaluation of entities, especially when it comes to rate limits.
* We’ve updated all docs links in the application to go to [our docs](https://docs.cortex.io/index.md) instead of the help desk. Going forward, new [walkthroughs](https://docs.cortex.io/docs/walkthroughs) & guides will only be added here.
* We’ve added toggles to Settings → Workspace → Notifications to give users control over notifications for the the new Entity Verification feature. Both Verification Period Start and Reminder notifications can be enabled or disabled here.

**Bug fixes** 🐛

* We’ve fixed an issue with the logic around sending recurring notifications for initiatives that resulted in notifications being sent more frequently.
* CQL reports now show “\[]” for empty lists, instead of an empty column

**July 30, 2024**

**Improvements** 📈

* The flow for editing the relationships of domains and teams in the UI has been streamlined. Parents and children of both types of entities can now be edited from the UI, regardless of whether the relationship is defined in the parent or child definition.
* We’ve added support for issues from ClickUp in the the dev homepage. As part of this, we’ve also added the ability to map users from ClickUp to Cortex, with a corresponding page in settings.
* In order to pull in GitHub issues to Cortex, you’ll need to update permissions to include read & write access for issues.

**Bug fixes** 🐛

* Fixed an issue with groups not being handled properly if specified in the Entity Data Verification feature configuration.
* Fixed a bug which sometimes caused a “Could not find workflow run action” error message to be displayed when executing a workflow.
* Code reviews where you are the author are no longer included in the weekly report.
* Fixed validation on the Create catalog page to not allow uppercase characters in the URL of the catalog.
* Fixed an issue which caused too many error messages to be displayed when encountering an error with an integration on an Entities list page.
* Fixed a continuous UI loop that could cause flickering on an Initiative page after creation.

**July 23, 2024**

**New Relic Open Telemetry support:** You can now pull in Open Telemetry data from New Relic for entities by adding a New Relic service’s tag and value information into the entity YAML. Once added, you’ll see Open Telemetry data in the entity page and can include it in Scorecards using the existing `newrelic.rawNrql` expression. To learn more, take a look at [our docs](https://docs.cortex.io/docs/reference/integrations/newrelic.md#opentelemetry) & the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=New%20Relic\&path=Raw%20NRQL%20query).

**GitHub issues integration:** We’ve added support for pulling issues from GitHub. You can see an entity’s issues in the GitHub issues tab from its corresponding repository and evaluate them in CQL using `github.issues()`, as well as see any issues assigned to you in the developer homepage. If you have an ongoing Initiative, you can create GitHub issues by adding an issue configuration. To learn more about the integration, take a look at our GitHub docs.

**Improvements** 📈

* In the Eng Intelligence settings page, you can now exclude certain author names from being included in the metrics. By default, we exclude any pull requests opened by bots in GitHub.
* We’ve updated the welcome messages that a user receives when first logging into Cortex and after 2 and 6 weeks.
* We’re moved the filters on the catalog, entity, Scorecard & Initiatives pages to the top right to give list pages more space.

**July 18, 2024**

**Provider field is now required for group-based ownership in entity YAMLs**

Any group type owners in the x-cortex-owners section of an entity descriptor will require a provider to be explicitly defined. The provider refers to the source where the member information for the group should be pulled from (for example, a specific Cortex team entity, or a GitHub or Okta group). Historically, if no provider was defined, we would automatically try to disambiguate the team provider, which could lead to indeterminate behaviors in ownership. We are making this optional field required to ensure clearer behaviors around entity ownership.

Beginning with this release, these warnings are now errors and affected YAMLs will no longer be processed. Most entities should not be affected by this change as entities imported or modified through Cortex have this field already set.

You can run this CQL query in the Query Builder (select all entities) to find any entities that are affected:

`jq(entity.descriptor(), "[.info.\"x-cortex-owners\" | .[] | select(.type | ascii_downcase == \"group\") | select(.provider == null)] | length") > 0`

You can find more information about ownership for entities in our [public docs](https://docs.cortex.io/docs/reference/basics/ownership).

**July 16, 2024**

**Entity data verification flow:** We’ve added native capabilities to support entity data verification in the app directly. This will be extremely helpful for compliance or audit requirements to ensure entity ownership and metadata is accurate and up to date. You can define verification periods along with verification owners. Once enabled, those verifiers will receive notifications to verify entities they own and mark their assessment in- app. CQL reports can be created to track the last verified timestamp for each entity. Learn more about entity verification & setting it up in [our docs](https://docs.cortex.io/docs/walkthroughs/workspace-settings/entity-verification.md).

**New Relic SLO support:** You can now pull in SLOs from New Relic for entities. You’ll see SLOs in the NewRelic entity page as well as the Operations tab and include [rules in Scorecards to check for SLOs](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=New%20Relic\&path=SLOs). Learn more in [our docs](https://docs.cortex.io/docs/reference/integrations/newrelic.md#slos).

**Improvements** 📈

* We’ve added a new input to Workflows that allows the user to choose from the list of available Slack channels.
* We’re moving filters to the top right to give list pages more space, starting with moving the catalog page filters.
* We are now showing email owners in the overview of an entity

**Bug fixes** 🐛

* We’ve made various improvements to the Initiatives details page to improve performance.
* We’ve fixed an issue with using hierarchy in a Workflow user input when only allowing one selection
* We’ve fixed a bug with adding new Scaffolder variable overrides in Workflows not clearing previous override data
* We’ve fixed a bug with CQL reports that was causing the whole report to error out in the case of an error with a CQL expression in the report.
* We’ve fixed a bug with links in CQL reports not being hyperlinked properly in JSON objects.
* We’ve fixed a bug with infinite scrolling in CQL reports making the last few items not render.
* We’ve fixed a bug where deleting an entity’s deployment via UUID was deleting all deploys. It now only deletes the intended deployment.
* The events page filter is now inclusive of the start & end date.

**July 10, 2024**

**SCIM support through Okta:** We’ve simplified and automated user provisioning and de-provisioning via a SCIM protocol with Okta. To do so, simply follow our [SCIM guide](https://docs.cortex.io/docs/setup/scim/okta) & enable Okta deprovisioning and provisioning in the [SCIM settings page](https://app.getcortexapp.com/admin/settings/scim).

**Improvements** 📈

* We’ve added more flexibility to the [Workday integration](https://docs.cortex.io/docs/reference/integrations/workday). After entering your Workday credentials you will be prompted to map the fields from your Workday report to Cortex fields. This allows Cortex to be more flexible in how we import Workday teams and their corresponding hierarchies to give you the most flexibility. If you’re using the old report format, no action is required.
* Team dropdowns throughout Cortex now display information about the number of members a team has.
* We’ve made some performance improvements to the Initiatives page.
* We’ve added verbose audit logging to Scorecard metadata and rule changes
* We’ve added viewing audit logs as a new permission that can be assigned to custom roles. This is now separate from our edit Settings permission.
* The AWS settings page will now show validation for all configured accounts by default. If we run into any errors while trying to pull details for any configured entity types, you’ll be able to see the missing roles in the Settings page.

**Bug fixes** 🐛

* We’ve fixed an issue with saving description for CQL reports
* The archival toggle in the catalogs will now work as expected

**July 2, 2024**

**Audit log enhancements:** Our audit logs now include information about what changed for the entity when you click on the row. We’ve also added the ability to filter by actor, activity type, and entity as well as adding support for changes to the IP allowlist and secrets in Settings. **Part of this effort includes an updated retention policy of up to 30 days. If you would like a longer retention period, please contact your customer success manager.**

**June 25, 2024**

**Improvements** 📈

* We’ve updated the content across our three Initiative related notifications (creation, recurring progress, and final day reminders) to be more consistent with each other.
* We’ve added pagination support for the public API endpoints to [list all plugins](https://docs.cortex.io/docs/api/list-all-plugins) and [get the discovery audit report](https://docs.cortex.io/docs/api/get-discovery-audit). We highly recommend updating any workflows using this endpoint.
* We’ve made performance improvements to the Scorecard rule exemptions page in Settings.
* We’ve improved our validation for URLs when configuring integrations through Settings.

**Bug fixes** 🐛

* We fixed an issue with the plugin preview when testing it out for both global & entity scope.

**June 18, 2024**

**Scorecard rules and CQL**

* We’ve added tags to the `azureResource.details()` object in CQL

**Improvements** 📈

* When using templated messages in Scorecard rule descriptions & failure messages, you’ll now be able to make use of autocomplete for captures.
* We’ve added pagination support for the public API endpoints to [list groups for an entity](https://docs.cortex.io/docs/api/list-groups-for-entity), [list custom events for an entity](https://docs.cortex.io/docs/api/list-custom-events-for-entity), [list dependencies for an entity](https://docs.cortex.io/docs/api/list-dependencies-for-entity), [list entity types](https://docs.cortex.io/docs/api/list-definitions), [list configured allowlist](https://docs.cortex.io/docs/api/list-allowed-ip-addresses). We highly recommend updating any workflows using this endpoint.
* The dropdown for adding owners to an entity will now display all users from all enabled identity providers, rather than just showing the users who have logged into Cortex.
* In Workflows there are two new inputs available. One is a Cortex Entity input that allows the user to choose from a custom-filtered list of entities, and the second allows selection from the full list of users
* We’ve enhanced the performance and added more filtering options to the Audit Log feature.

**Bug fixes** 🐛

* The API endpoint to [Retrieve OpenAPI docs for entity](https://docs.cortex.io/docs/api/get-open-api-doc-for-entity) has been updated to more closely reflect the behavior of API Explorer. Now, if an entity does not have an OpenAPI spec uploaded, the endpoint will return an OpenAPI spec defined in entity YAML (as an `x-cortex-link`). For entities where multiple OpenAPI specs have been defined, a new `name` parameter has been added to retrieve the right one.

**Collapsible sidebar navigation**

**Sidebar navigation:** To round out the work we’ve done to move our main header to the sidebar, you are now able to collapse it. If you’re an admin, you can specify a new logo in the [appearance tab](https://app.getcortexapp.com/admin/settings/appearance). This is displayed for all users when the sidebar is collapsed.

**June 13, 2024**

**Global & regional support for AWS**

We’ve added support for global & regional resources from AWS:

* Resources of type AWS::S3::Bucket will have the ‘region’ field accurately reflect the physical location of your buckets as specified in AWS account. If you are using custom AWS Policy, please make sure that all accounts have the s3::GetBucketLocation policy.
* Global resources like AWS::IAM::, AWS::Cloudfront::, AWS::Route53:: will have the ‘region’ field set to null to indicate their global accessibility and applicability across all AWS regions.

**June 11, 2024**

**Templated messages in Scorecards:** You can now create more tailored descriptions and failure messages to make it easier for developers to understand how to act on the rule. Entity information and data from the CQL rule evaluation are available to use through template variables. For example, you can use this to dynamically generate links using the entity details or call out why they’re failing the rule (using captured values from the CQL expression).

To read more about setting up captures, take a look at the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Captures).

**Search improvements**: We’ve added support for searching for the entities a user owns by typing their name or email (e.g. **`owner:"Cristina Buenahora”`** or **`owner:"cristina.buenahora@cortex.io"`**) when using “Advanced search”.

We’ve also added support for querying for entities in the public API using the query param in the [list entities endpoint](https://docs.cortex.io/docs/api/list-all-entities). It’ll work the same way as searching in the catalog & return the results in order of relevance.

**Changes for catalogs with hierarchies:** We’ve added another “drill down mode” view option in the catalogs page. With the new Expandable list view, you can quickly see your rolled up hierarchical catalogs at a glance.

**Improvements** 📈

* We’ve added a new ‘Cortex Entity’ input type to Workflows, allowing an action to prompt the user to choose one or more entities within the Cortex platform. Those chosen entities will then be available to later actions in the flow just like other input types.
* We’ve been working on improving our handling of rate limits, which will both avoid customers seeing errors and lessen the likelihood that Cortex will use all of their capacity. We have introduced improved outbound throttling on CQL operations to limit the number of rate limit responses. A few weeks ago, we rolled out improvements for GitHub, GitLab, Pagerduty, Opsgenie, Datadog, and Snyk. Most recently, we added Bitbucket to the list. These changes will result in better success rates for jobs and allow us to scale up our worker fleet.
* We now support [approving](https://docs.cortex.io/docs/api/approve-scorecard-rule-exemption), [denying](https://docs.cortex.io/docs/api/deny-scorecard-rule-exemption), and [revoking](https://docs.cortex.io/docs/api/revoke-scorecard-rule-exemption) rule exemptions through the public API.

**June 4, 2024**

**Recurring initiative progress notifications:** You can now set up [recurring initiative progress notifications](https://docs.cortex.io/docs/walkthroughs/getting-started/initiatives-action-items#progress-notifications) to encourage action against an Initiative. When creating an Initiative, you can set the cadence for these recurring notifications and edit them as needed. These notifications will be sent to any users who have outstanding action items for the Initiative.

**Email notifications support:** Notifications are important to making progress on Scorecards & initiatives. We’ve added support for email notifications as an additional notification channel. Email notifications are disabled by default but can be enabled by going to the Notification Settings page at both the [workspace](https://app.getcortexapp.com/admin/settings/notifications) & [user](https://app.getcortexapp.com/admin/settings/notification-subscriptions) level. Additionally, we have updated Notification Settings to accommodate the three possible channels: Slack, MSTeams, and email and give you more control.

**Scorecard rules and CQL**

* We’ve added support for verifying if Veracode or Mend is configured for entities using `veracode != null` and `mend != null`

**Improvements** 📈

* We’ve rolled out significant performance improvements to the Bird’s eye report page.
* We’ve enhanced the filters in Audit Logs. You can now filter by actions, activity types, entities, and actors (including actor types, API key identifiers like API key names or the last 4 characters of the API key, emails, IP addresses, and anonymous request types).
* We’ve added links to CircleCI pipelines in the entity page.
* We’ve added support for specifying a region when configuring the Snyk integration. The default region is USA.
* We’ve added new icons for AWS resources to better help you differentiate between all the different entities.

**Bug fixes** 🐛

* We’ve fixed a bug with copying draft Scorecards.

**May 29, 2024**

**Improvements** 📈

* If you have AWS configured, we’ll now pull in the account alias from AWS alongside the AWS account ID. Please make sure the role has the `iam:ListAccountAliases` permission. The AWS account ID filter in the catalogs shows both name & ID if we have the account name.
* We’ve added a copy button to CQL reports

**May 28, 2024**

**Sidebar navigation**

**Sidebar navigation:** Over the years, we’ve added a lot of functionality in Cortex and our main header has become bloated. We’ve moved our header to the side. It contains all existing navigation items.

As part of this change, our resource center & product updates have moved to the right.

**May 21, 2024**

**CircleCI integration:** We’ve added [CircleCI](https://circleci.com/) to our list of integrations! You can now see metrics & recent pipeline runs for your CircleCI projects in the entities page and include CircleCI rules in [Scorecards](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=CircleCI). To set it up, simply add your API key in the [Settings page](https://app.getcortexapp.com/admin/settings/circleci) and add custom data fields to your YAML files in the **`x-cortex-circle-ci`** section. Take a look at the [docs](https://docs.cortex.io/docs/reference/integrations/circleci.md) for more information.

**Improvements** 📈

* We’ve rolled out a handful of exciting improvements to Workflows, including: *If you don’t have Workflows enabled, please reach out to your customer success manager.*
  * The action identifier (or slug) is now displayed below the action name on the Workflow graph for easier reference.
  * Individual inputs on an Input action can now be reordered by dragging-and-dropping.
  * Searching for workflows is now case-insensitive.
* We’ve been working on improving our handling of rate limits, which will both avoid customers seeing errors and lessen the likelihood that Cortex will use all of their capacity. We have introduced improved outbound throttling on CQL operations to limit the number of rate limit responses. So far, we’ve rolled out improvements for GitHub, GitLab, Pagerduty, Opsgenie, Datadog, and Snyk. These changes will result in better success rates for jobs and allow us to scale up our worker fleet.
* Our [Microsoft Teams app](https://appsource.microsoft.com/en-us/product/office/WA200005959) now supports team notifications. Microsoft Teams channels associated to teams in Cortex will now receive a notification when an Initiative is created if entities they own are included and a weekly report with the on-call schedule, and recommendations based on Scorecards and Initiatives. We expect this to drive additional visibility and progress for Scorecards and Initiatives.
* We’ve improved the validation and overall editing experience when modifying entities via the UI
* We’ve condensed the on-call section of the weekly report notification
* We’ve rolled out performance improvements to the Scorecard rule exemptions page in Settings

**Bug fixes** 🐛

* We’ve fixed a bug with the copy Scorecard rule button
* We’ve fixed the validation when adding a team member from your workspace
* We made a fix to pre-populate the team owner when editing ownership for entities

**May 14, 2024**

**Scorecard rules and CQL**

* We’ve added support for [custom events in CQL](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Service%20metadata\&path=Custom%20events). Custom events for entities can be added through the [public API](https://docs.cortex.io/docs/api/list-custom-events-for-entity).

**Improvements** 📈

* You can now drag-and-drop actions in any Workflow to reorder the steps. You’ll receive a warning if the new order may cause problems (for example, if an action is being moved before another action who’s output it depends on). *If you don’t have Workflows enabled, please reach out to your customer success manager.*
* We’ve made performance improvements to fetching the list of teams when editing an entities owners.
* The Discovery Audit report is now paginated, making it significantly faster to audit changes to your workspace.
* If you’re pulling in resources of type S3 & KMS Key, we’ll now display additional details in the entity page. If you do not see additional details, please make sure the account has the `kms:ListAliases` permission.
* If you’re using VictorOps for on-call, clicking on a user will now direct you to the corresponding users page in VictorOps.
* URLs for Initiatives will now update as you filter to enable easy sharing & bookmarking.

**May 7, 2024**

**Rule exemptions settings in Scorecards:** You can now configure whether rule exemptions are enabled and/or auto-approved for Scorecards. This is exposed in the UI when creating and editing Scorecards & in the YAML.

Rule exemptions for Scorecards are now included in the [list Scorecards](https://docs.cortex.io/docs/api/list-scorecards) & [get Scorecards](https://docs.cortex.io/docs/api/get-scorecard) endpoints in the public API. You can also request rule exemptions through the public API.

**Improvements** 📈

* We’ve updated filters in plugins, actions, and initiative issue configuration to support selecting entity types to include or exclude, allowing you to mix entity types in a single report, similar to how filtering works in the catalogs.
* We’ve rolled out performance improvements when fetching all Scorecards.
* We’ve improved the performance and responsiveness while running a Workflow.
* URLs for Scorecards will now update as you filter to enable easy sharing & bookmarking.

**Bug fixes** 🐛

* The deploys in the drilldown for Eng Intelligence metrics now match the deploys in the entity pages.
* We’ve fixed an error encountered when duplicating a Scorecard and subsequently modifying the Scorecard filter.
* Entities will now display their corresponding icon in the catalog pages.
* We’ve fixed back navigation from a sub-page of an entity overview to properly return to the entity overview page.

**April 28, 2024**

**Entity editing based on team ownership:** You can now limit editing of entities to certain team members who own the corresponding entities. In order to enable this, you’ll want to toggle “Team ownership entity editing” in the [Teams tab under Settings → Entities](https://app.getcortexapp.com/admin/settings/entities?activeTab=Teams). You’ll be able to specify team editors in the members tab in the teams page. Read more about setting this up in our [Help Desk guide](https://support.getcortexapp.com/hc/en-us/articles/25061055804059-Team-ownership-entity-editing).

*Note: This is not supported for GitOps and editors are not configurable through the YAML.*

**Improvements** 📈

* The [list Scorecards public API endpoint](https://docs.cortex.io/docs/api/list-scorecards) now supports pagination. We highly recommend updating any workflows using this endpoint.

**April 26, 2024**

**Catalog changes:** We have released pagination for catalog pages. This will improve the initial load of a catalog and the performance when searching or filtering a catalog. As previously announced, part of this effort will impact previously bookmarked catalog page urls that referenced filters. Those urls will be broken and we recommend updating them.

**Improvements** 📈

* If there are multiple changes to on-call, you’ll receive one notification with details for all changes.
* We’ve rolled out performance improvements for the initial load of the dependency graph.

**Bug fixes** 🐛

* We’ve fixed a bug with adding a CQL filter to initiatives.

**April 22, 2024**

**Scorecard rule identifiers:** We’ve added support for identifiers in Scorecard rules. These will be exposed:

* In the Scorecard rules tab alongside the rule title, expression, and metadata.
* In the [Scorecard YAML](https://docs.cortex.io/docs/reference/basics/scorecards#descriptor) when you export the Scorecard
* In the Scorecard responses in the [public API](https://docs.cortex.io/docs/api/list-scorecards)

If you have UI editing enabled, identifiers will be automatically created for Scorecard rules and cannot be edited.

If you have GitOps enabled, you’ll be able to define a Scorecard rule identifier. If you do not, one will be automatically assigned and you’ll be able to export the Scorecard YAML through the UI. When the unique identifiers are updated, the corresponding rule will be treated as a brand new rule and any previously approved rule exemptions will be invalid.

**Improvements** 📈

* When using the “Advanced search” in the catalogs, you can now search for the entities a user owns by typing their name or email (e.g. `member:"Cristina Buenahora”` or `member:"`[`cristina.buenahora@cortex.io`](mailto:cristina.buenahora@cortex.io)`"`)
* The [list deploys for entity public API endpoint](https://docs.cortex.io/docs/api/get-deploys-for-entity) now supports pagination. We highly recommend updating any workflows using this endpoint.
* Admins can now configure the default view for the relationships graph in the [Appearance tab under Settings](https://app.getcortexapp.com/admin/settings/appearance?activeTab=Relationship%20graphs).
* When looking at the domains or teams visualization, you now have the option to toggle whether you want to see archived entities. By default, they are hidden.
* We’ve updated filters in CQL reports to support selecting entity types to include or exclude, allowing you to mix entity types in a single report, similar to how filtering works in the catalogs.
* We’ve updated our [Workday integration](https://docs.cortex.io/docs/reference/integrations/workday#setup) to support teamSupervisoryOrgId and employeeSupervisoryOrgId. When these fields are defined, we will use the them to create the hierarchy instead of relying on the manager of a team. Additionally, we’ve lifted the restriction that someone can only be part of one team. If someone is in multiple teams, you’ll just need to ensure there is a row for that person for each team they’re a part of.

**Bug fixes** 🐛

* We’ve made improvements to how we handle syncing dependencies from Azure Resources

**April 16, 2024**

**Improvements** 📈

* We’ve made some platform changes to how we handle background tasks, including Scorecard, CQL report, and query builder evaluations, that will improve the slowness that impacted various evaluations in the last few weeks.
* We’ve rolled out performance improvements for the teams leaderboard and fetching Scorecards for entities.

**Bug fixes** 🐛

* Entities will no longer be archived if the YAML file is being moved between folders
* We’ve fixed the `firehydrant != null` expression to take auto-guessing into account
* We’ve fixed a “missing Sentry registration” error in CQL

**April 9, 2024**

**Scorecard rules and CQL**

* We’ve added support for `.split()` to strings in CQL v2

**Improvements** 📈

* You can now create complex filters for initiatives, similar to what we support for Scorecards.
* Our multi picker for selecting entities can now handle thousands of entities. This will result in a snappier experience when selecting entities in the create & edit domain pages or relationships graph.
* The YAML linter will provide warnings if `x-cortex-children` is invalid for an entity

**Bug fixes** 🐛

* We’ve implemented various fixes for the Scorecard rule form when creating or editing Scorecards
* We’ve fixed an error with copying resource Scorecards
* We’ve fixed various issues when fetching GitLab groups that occasionally resulted in timeouts. As part of these fixes, we’ve also improved performance around fetching GitLab groups.
* All archived teams are now filtered out from the Bird’s eye & all Scorecard reports
* Archived entities will no longer be included in notifications

**April 2, 2024**

**Teams visualization** – Similar to the domains visualization view that we released a few weeks ago, you can now view team hierarchies in the relationship graph. This graph supports a tree visualization with search, filters, and display options (like overlaying Scorecard progress). You can zoom in and out of the graph to see all the relationships built through the team entity - it’s great for onboarding a new person onto the team or visually searching for who owns an entity.

**Syncing ownership tags from AWS** – A few weeks ago, we released support for bringing in tags from AWS to keep track of ownership of resources. By default, we look for the “owner” tag. We’ve now added support to customize the tag name. To enable this feature, enable the “Sync ownership from AWS” toggle in [AWS Settings page](https://app.getcortexapp.com/admin/settings/aws).

**Improvements** 📈

* We’ve added more visibility to CQL reports. You’ll now see all entities evaluated including the error we encountered, such as rate limits, in the report.
* Admins now have the ability to decide which entity types can be imported through the UI in the [GitOps tab in the Entities Settings page](https://app.getcortexapp.com/admin/settings/entities?activeTab=GitOps). Any types that cannot be imported will not be shown during the import flow. If all are disabled, users will no longer see the import entities button at all.
* [AWS](https://docs.cortex.io/docs/api/aws-get-aws-cloud-control-types) and [Azure Resource](https://docs.cortex.io/docs/api/azure-resources-list-azure-resource-types) configured types to be discovered & pulled into the catalogs can now be managed through the public API.
* URLs for Eng Intelligence and the developer homepage will now update as you filter to enable easy sharing & bookmarking.

**Bug fixes** 🐛

* We’ve fixed an issue where the Bird’s Eye report was not properly handling inherited ownership in certain cases when applying team & domain hierarchies
* If auto archiving for entities is enabled, we’ll now properly archive those entities when their corresponding YAML files are deleted
* We’ve fixed a bug when exporting Scorecards with group filters
* Users with permissions to configure plugins will now be able to see and edit all draft plugins

**March 26, 2024**

**Automatic deprovisioning of users for Okta:** Cortex can now automatically deprovision users if you’re using Okta for SSO & identity management. This is based on a sync job that runs once a day at 10 AM UTC. You’ll be able to see a list of users removed in [audit logs](https://app.getcortexapp.com/admin/settings/audit-logs).

In order to enable this, you’ll have to set up Okta in the [Open ID Connector settings page](https://app.getcortexapp.com/admin/settings/oidc) as well as the [Okta integration](https://app.getcortexapp.com/admin/settings/okta) and enable the toggle to automatic deprovision users.

**Improvements** 📈

* The [list all entities public API endpoint](https://docs.cortex.io/docs/api/list-all-entities) now supports pagination. We highly recommend updating any workflows using this endpoint.
* The [list Scorecards public API endpoint](https://docs.cortex.io/docs/api/list-scorecards) returns filter information.
* Team names synced automatically from the Workday integration will update to stay in sync with the report
* We’ve rolled out performance improvements for the discovery report.
* Team specific notifications, including the weekly report and initiative creation, are now supported for Microsoft Teams.

**Bug fixes** 🐛

* We’ve made improvements to the PagerDuty integration to prevent timeouts
* When using base paths for mono repos in Azure Devops, clicking on the repository will now take you to the correct path

**March 19, 2024**

**Auto archival of entities:** Cortex can now auto archive any entities when they are no longer detected in your integrations or whose corresponding YAML files are deleted. For example, if you use AWS to auto-hydrate your catalogs, enabling this feature will automatically archive entities that are deleted in AWS. To set this up, simply toggle it in the [entities Settings page](https://app.getcortexapp.com/admin/settings/entities).

**Bitbucket multi-instance support:** If your organization has multiple instances of Bitbucket, you can now configure all of them in the Settings page. This will allow you to discover and import services from all repositories across all configured Bitbucket accounts.

**Jira multi-instance support:** If your organization has multiple instances of Jira, you can now configure all of them in the Settings page. This will allow you to pull in Jira information for entities and create Jira tickets for initiatives across all configured Jira accounts.

**Improvements** 📈

* If you’re using Okta for SSO, you can enable automatic automatic user deprovisioning in the [Okta settings page](https://app.getcortexapp.com/admin/settings/okta). This is based on a sync job that runs once a day at 10 AM UTC. You’ll be able to see a list of users removed in audit logs.
* We’ve added permissions for viewing & creating CQL reports and viewing & sending messages in onboarding management. You can include or exclude any of these permissions from custom roles.
* We’ve rolled out various performance improvements to team pages & the operations tab for entities.
* When importing or editing entities, you can add their corresponding parent domain.

**Bug fixes** 🐛

* GitHub app installation errors will be displayed during the configuration flow.

**March 12, 2024**

**Performance is a mindset** 🧠

The theme du jour over here at Cortex has shifted a bit towards helping everyone access all the features they know and love a bit faster. We’ve started rolling out performance improvements to many needed areas of the app.

**Scorecard rules and CQL**

* More expressions are now able to be auto-migrated from CQL v1 to CQL v2 during Scorecard evaluation

**Improvements** 📈

* Snyk issues are now displayed in a sortable table layout
* If a regularly scheduled integration config validation encounters a rate limit error, propagate the previous status instead of updating to an error
* The expression associated with a rule exemption is now returned in the public API

**Bug fixes** 🐛

* Fixed an issue where GitLab reviewers were not correctly being associated with users, causing blank spots on the Dev Homepage
* Fixed an issue causing an unexpected description to display for a team
* Improved the matching of Scorecard rules whose expression is changing in GitOps processing

**March 6, 2024**

**Syncing ownership tags from AWS** – Keeping entity YAMLs and ownership information can be tedious if resources are updated frequently. To alleviate some of that upkeep, the AWS integration can now bring in AWS tags into Cortex. This will help keep entities in Cortex up to date with the latest ownership information inherited from AWS. To enable this feature, enable the “Sync ownership from AWS” toggle in the teams tab of the [Entities Settings page](https://app.getcortexapp.com/admin/settings/entities).

**Domains visualization** – We’ve introduced a better way to visualize and interact with your domain hierarchies via a domains relationship graph. This graph, like our dependency graph, supports a tree visualization with search, filters, and display options (like overlaying Scorecard progress). You can zoom in and out of the graph to see all the relationships built through the domain entity - it’s great for onboarding a new person onto the team or visually searching for who owns an entity.

**Scheduled Scorecard rules**  – You can now define a future Scorecard evaluation date timestamp for rules. This feature is particularly helpful when you’re preparing a new rule(s) that you want to share with your team ahead of including it in the Scorecard score evaluation. You are able to define one or more scheduled rules for any level or level-less scorecard(s). When a new rule has been scheduled, a notification will be sent to the user and teams affected. Ahead of the rule evaluation start date, a reminder notification will also be sent 7 days and 1 day before.

**Scorecard rules and CQL**

* We’ve added support for `k8s.clusters()` . You can take a look at example expressions in the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Cluster%20information).

**Improvements** 📈

* We’ve unified members & additional members in the edit page for teams into one.

**February 27, 2024**

**Scorecard rules and CQL**

* We’ve added support for isArchived to the [children](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Domain%20metadata\&path=Hierarchy%3A%20children) and [parent](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Domain%20metadata\&path=Hierarchy%3A%20parents) object for teams and domains. This will allow you to check whether a domain or team has any children or parents that are archived. Note: This is only available in CQL v2.0.

\*\* *In case you missed it: We’ve been working on a new-and-improved major version of CQL with tons of improvements, including better UX and tooling (autocomplete, syntax highlighting, and more). You can see the full summary of changes for CQL v2.0* [*here*](https://support.getcortexapp.com/hc/en-us/articles/20882617525403-CQL-v2-0)*. When you’re ready to upgrade, reach out to Cortex Customer Success to get CQL v2.0 enabled. With the availability of CQL v2.0, new metrics and features will be added to v2.0 only by default. CQL v2.0 is currently in a stable beta and we’d love your feedback on the updated language.*

*Once enabled, we’ll automatically try to migrate any v1.0 expressions the next time a Scorecard or CQL report is evaluated. If GitOps for Scorecards is enabled or we can’t auto migrate, anyone who can edit Scorecards or CQL reports will see a yellow warning indicator ⚠ next to any v1.0 expressions and be prompted to migrate. We’ve written a guide for* [*migrating to CQL v2.0*](https://support.getcortexapp.com/hc/en-us/articles/20992192357275-Migrating-to-CQL-v2-0)*, and the*[*CQL explorer*](https://app.getcortexapp.com/admin/cql-explorer)*is a good resource for how the language works with examples. Please reach out to our team for guidance if needed as well.*

**Improvements** 📈

* We’ve added permissions for configuring Scaffolder templates and running the Scaffolder. You can add these to users and teams in the [roles and permissions Settings page](https://app.getcortexapp.com/admin/settings/permissions).
* We’ve added descriptions to all permissions in the [roles and permissions Settings page](https://app.getcortexapp.com/admin/settings/permissions)
* Active incidents from [incident.io](http://incident.io) will now be included in the overview and operations tabs of an entity page

**Bug fixes** 🐛

* We’ve fixed an error when syncing teams and members from Azure Active Directory that was preventing the list of users from being displayed in the Identity Mappings page

**February 21, 2024**

**Eng Intelligence Metrics Traceability:** Eng Intelligence now “shows its work” by letting you see exactly which events it used to calculate the metrics. To view the events associated with a particular metric, you can either click the metric in the table to navigate directly to those events in the side panel, or click a row to expand the side panel and view the events in the “Recent activity” tab of the side panel. Note: Eng Intelligence is available as an add-on to Cortex.

**Scorecard rules and CQL**

* We’ve added support for `entity.isArchived()` and [isArchived to the dependency object](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Service%20metadata\&path=Dependencies\&path=Incoming%20dependencies) so that you can check whether an entity has any archived dependencies. The expression to do so is `dependencies.out(includeArchived = true).any((dependency) => dependency.isArchived == true)` . Note: This is only available in CQL v2.0.

\*\* *In case you missed it: We’ve been working on a new-and-improved major version of CQL with tons of improvements, including better UX and tooling (autocomplete, syntax highlighting, and more). You can see the full summary of changes for CQL v2.0* [*here*](https://support.getcortexapp.com/hc/en-us/articles/20882617525403-CQL-v2-0)*. When you’re ready to upgrade, reach out to Cortex Customer Success to get CQL v2.0 enabled. With the availability of CQL v2.0, new metrics and features will be added to v2.0 only by default. CQL v2.0 is currently in a stable beta and we’d love your feedback on the updated language.*

*Once enabled, we’ll automatically try to migrate any v1.0 expressions the next time a Scorecard or CQL report is evaluated. If GitOps for Scorecards is enabled or we can’t auto migrate, anyone who can edit Scorecards or CQL reports will see a yellow warning indicator ⚠ next to any v1.0 expressions and be prompted to migrate. We’ve written a guide for* [*migrating to CQL v2.0*](https://support.getcortexapp.com/hc/en-us/articles/20992192357275-Migrating-to-CQL-v2-0)*, and the*[*CQL explorer*](https://app.getcortexapp.com/admin/cql-explorer)*is a good resource for how the language works with examples. Please reach out to our team for guidance if needed as well.*

**Improvements** 📈

* We’ve enhanced the filters in Eng Intelligence. Note: Eng Intelligence is available as an add-on to Cortex.
* We’ve added `lastUpdated` to the Scorecards response in the [public API](https://docs.cortex.io/docs/api/list-scorecards). This includes setting the next evaluation time.
* Plugin user context now includes the current user’s roles. See the updated typing in `@cortexapps/plugin-core@^2.2.1`

**Bug fixes** 🐛

* Insights in the developer homepage will show the next level for an entity for a Scorecard
* We’ve fixed an error showing up on the events page if you have GitLab vulnerabilities
* Plugin context TypeScript typing no longer erroneously reports a non-existent `role` field (as of `@cortexapps/plugin-core@^2.2.1`)

**February 17, 2024**

**BREAKING CHANGE – Package processing changes:** Until now, Cortex has been processing package dependencies from package-lock version 3 files using the whole path to the package, which may include one or multiple levels of `node_modules/`. We’ve updated our processor to parse out only the actual package name from the path to correctly represent the package. This may affect existing CQL expressions (such as those on Scorecard rules) if any are written in a way with the directory path in mind. *Note: Our team has reached out to anyone with impacted Scorecards.*

A pair of examples:

* `node_modules/@babel/code-frame/node_modules/chalk` becomes `chalk`
* `node_modules/@babel/core` becomes `@babel/core`

As always, feel free to reach out with questions or for assistance!

**February 13, 2024**

**Team notifications:** Slack channels associated to teams in Cortex will now receive a notification when an Initiative is created if entities they own are included and a weekly report with the on-call schedule, and recommendations based on Scorecards and Initiatives. We expect this to drive additional visibility and progress for Scorecards and Initiatives. To enable these notifications, you’ll have to uninstall & reinstall the Slack app to apply the new scopes required to send these notifications.

**Bulk editing for roles & permissions:** You can now change roles & permissions for multiple users or teams at the same time. When updating permissions, we’ll let you know if you’re removing a particular user’s permission to prevent mistakes. You can also bulk delete users and teams.

**Scorecard rules and CQL**

* We’ve added support for getting the timestamp of when an entity was created or updated using `entity.created(asTimestamp = true)` and `entity.lastUpdated(asTimestamp = true)` . Note: This is only available in CQL v2.0.

\*\* *In case you missed it: We’ve been working on a new-and-improved major version of CQL with tons of improvements, including better UX and tooling (autocomplete, syntax highlighting, and more). You can see the full summary of changes for CQL v2.0* [*here*](https://support.getcortexapp.com/hc/en-us/articles/20882617525403-CQL-v2-0)*. When you’re ready to upgrade, reach out to Cortex Customer Success to get CQL v2.0 enabled. With the availability of CQL v2.0, new metrics and features will be added to v2.0 only by default. CQL v2.0 is currently in a stable beta and we’d love your feedback on the updated language.*

*Once enabled, we’ll automatically try to migrate any v1.0 expressions the next time a Scorecard or CQL report is evaluated. If GitOps for Scorecards is enabled or we can’t auto migrate, anyone who can edit Scorecards or CQL reports will see a yellow warning indicator ⚠ next to any v1.0 expressions and be prompted to migrate. We’ve written a guide for* [*migrating to CQL v2.0*](https://support.getcortexapp.com/hc/en-us/articles/20992192357275-Migrating-to-CQL-v2-0)*, and the*[*CQL explorer*](https://app.getcortexapp.com/admin/cql-explorer)*is a good resource for how the language works with examples. Please reach out to our team for guidance if needed as well.*

**Improvements** 📈

* We’ve made various performance improvements to the domains catalog, developer homepage, and Scorecards pages.

**Bug fixes** 🐛

* We’ve fixed a bug with the CQL rule for checking that an entity has a Microsoft Teams channel associated with it

**February 6, 2024**

**Weekly report for teams:** We’ll now send teams that have a Slack channel configured a weekly report with the on-call schedule, and recommendations based on Scorecards and Initiatives. We expect this to drive additional visibility and progress for Scorecards and Initiatives. To enable these notifications, you’ll have to uninstall & reinstall the Slack app.

**Scorecard rules and CQL**

* We’ve added support for `entity.children()` and `entity.parents()` for team entities. With this, you can validate that your team hierarchy is set up as you expect. Note: This is only available in CQL v2.0.

\*\* *In case you missed it: We’ve been working on a new-and-improved major version of CQL with tons of improvements, including better UX and tooling (autocomplete, syntax highlighting, and more). You can see the full summary of changes for CQL v2.0* [*here*](https://support.getcortexapp.com/hc/en-us/articles/20882617525403-CQL-v2-0)*. When you’re ready to upgrade, reach out to Cortex Customer Success to get CQL v2.0 enabled. With the availability of CQL v2.0, new metrics and features will be added to v2.0 only by default. CQL v2.0 is currently in a stable beta and we’d love your feedback on the updated language.*

*Once enabled, we’ll automatically try to migrate any v1.0 expressions the next time a Scorecard or CQL report is evaluated. If GitOps for Scorecards is enabled or we can’t auto migrate, anyone who can edit Scorecards or CQL reports will see a yellow warning indicator ⚠ next to any v1.0 expressions and be prompted to migrate. We’ve written a guide for* [*migrating to CQL v2.0*](https://support.getcortexapp.com/hc/en-us/articles/20992192357275-Migrating-to-CQL-v2-0)*, and the*[*CQL explorer*](https://app.getcortexapp.com/admin/cql-explorer)*is a good resource for how the language works with examples. Please reach out to our team for guidance if needed as well.*

**Improvements** 📈

* The [endpoint to retrieve entity details](https://docs.cortex.io/docs/api/get-entity-details) now includes Slack channels
* We’ve added the repository URL to the Git object to the [entity object](https://docs.cortex.io/docs/api/list-all-entities) in the public API
* We’ve implemented various performance improvements for initiatives that can, in some cases, speed up initiatives load times by 10x
* We’ve added support for syncing [employee role from the Workday report](https://docs.cortex.io/docs/reference/integrations/workday)
* The “My catalog” tab in the developer homepage now has table headings
* Auto-populated tags in the UI will no longer include trailing slashes or spaces

**Bug fixes** 🐛

* The insights in the developer homepage show suggestions for Scorecards based on the next level
* We’ve fixed an issue with Azure Devops and Azure Active Directory on the My Integration Accounts page that was resulting in the page to crash.
* We’ve fixed a bug with the import button from the discovery audit

**January 30, 2024**

**My integration accounts page:** All users can now see their own personal integration mappings in [their Settings](https://app.getcortexapp.com/admin/settings/my-integration-accounts) and verify that they are correct.

**Eng Intelligence Scorecard:** The power of Eng Intelligence is now available in CQL! All customers can now access metrics around pull requests, incidents, and issues for use in Scorecards or one-off querying, and a Scorecard template is available with example pre-made calculations.

Note: These new metrics are only available in CQL v2.0. For a dashboard view with historical values and an easy break-down by different groups and more, the full Eng Intelligence feature must be purchased.

**Notification settings for Scorecards:** You can now specify whether or not you want to include individual Scorecards in [notifications](https://support.getcortexapp.com/hc/en-us/articles/19609570240539-Notifications).

If you’re using UI editing, you’ll see a notifications toggle in the metadata section. By default, draft Scorecards have notifications set to false. When Scorecards are published, notifications will be enabled.

If you’re using GitOps, you can specify notifications in the YAML:

```kotlin theme={null}

notifications:
  enabled: true

```

Whether or not notifications are enabled will be included in the [Public API responses](https://docs.cortex.io/docs/api/list-scorecards) as well.

If you choose to enable notifications for a draft Scorecard, only users with permission to edit the Scorecard will receive notifications. This allows you to test the notifications for a Scorecard without publishing it.

**Improvements** 📈

* We’ve overhauled the sync job that ingests AWS dependencies. As part of this overhaul, you will now see status of the sync jobs in the dependency graph page.
* If you’d like to restrict the Cortex Slackbot to allow access only to users with a valid account in your Cortex workspace, you can toggle this in the [Slack Settings page](https://app.getcortexapp.com/admin/settings/slack).

**Bug fixes** 🐛

* No longer shows existing team members as an option when adding new members to a team
* When filtering the executive report by department, the filter now includes entities directly owned by that department as well as entities owned by its descendants

**January 23, 2024**

**Suggestions for identity mappings:** We know that manually mapping users can be tedious, so we’ve added a suggestion based on name for unmapped users to all identity mapping pages. We recommend manually approving each suggestion to avoid accidentally granting permissions, but you do have the option to accept all.

**Scorecard rules and CQL**

We’ve been working on a new-and-improved major version of CQL with tons of improvements, including better UX and tooling (autocomplete, syntax highlighting, and more). You can see the full summary of changes for CQL v2.0 [here](https://support.getcortexapp.com/hc/en-us/articles/20882617525403-CQL-v2-0). When you’re ready to upgrade, reach out to Cortex Customer Success to get CQL v2.0 enabled. With the availability of CQL v2.0, new metrics and features will be added to v2.0 only by default. CQL v2.0 is currently in a stable beta and we’d love your feedback on the updated language.

Once enabled, we’ll automatically try to migrate any v1.0 expressions the next time a Scorecard or CQL report is evaluated. If GitOps for Scorecards is enabled or we can’t auto migrate, anyone who can edit Scorecards or CQL reports will see a yellow warning indicator ⚠ next to any v1.0 expressions and be prompted to migrate. We’ve written a guide for [migrating to CQL v2.0](https://support.getcortexapp.com/hc/en-us/articles/20992192357275-Migrating-to-CQL-v2-0), and the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer) is a good resource for how the language works with examples. Please reach out to our team for guidance if needed as well.

* We’ve added support for [incidents from PagerDuty to CQL](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=PagerDuty\&path=Incidents). With this, you can start measuring information about incidents, including how many were opened in the last month or how many took over 2 days to resolve. Note: PagerDuty incident metrics are only available in CQL v2.0.
* We’ve added support for [pull requests from GitHub or GitLab to CQL](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=GitHub\&path=Pull%20Requests) allowing you to check attributes about pull requests in Scorecards. Note: Git pull request metrics are only available in CQL v2.0.
* We’ve expanded `git.branchProtection` to support `disableOverridingApproversPerMergeRequest`, `mergeRequestsAuthorApproval`, `requiredStatusChecks`, and more for users with GitLab Ultimate. You can see the full branchProtection object in the [CQL explorer](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=GitLab\&path=Branch%20protection%20details). Note: advanced branch protection rules for GitLab are only available in CQL v2.0.
* We’ve added support for [additional SonarQube metrics](https://app.getcortexapp.com/admin/cql-explorer?path=CQL%20Explorer\&path=Integrations\&path=SonarQube\&path=Metric) including `security_hotspots`, `security_rating`, and more. Note: the new SonarQube metrics are only available in CQL v2.0.

**Improvements** 📈

* We’ve added an identity mapping page for Opsgenie.
* Cortex recommends using Google Chrome for the optimal experience. Users using other browsers will now see a modal on initial login suggesting that they switch. More information about our browser support can be found [here](https://support.getcortexapp.com/hc/en-us/articles/21415271221787-Cortex-browser-support).

**Bug fixes** 🐛

* Icons for entity dependencies are now properly displayed in the dependencies page
* Users will no longer see the API Explorer, Datadog, or Deploys tabs in the entity details side nav unless those pages have corresponding data
* We’ve fixed a bug with filtering teams on certain report pages, including the Bird’s Eye and All Scorecards reports

**January 16, 2024**

**Auto archiving of entities (including resources):** Cortex will now auto archive any entities when they are no longer detected in your integrations or whose corresponding YAML files are deleted. For example, if you use AWS to auto-hydrate your Resource catalog, enabling this feature will automatically archive resources that are deleted in AWS. To set this up, simply toggle it in the [entities Settings page](https://app.getcortexapp.com/admin/settings/entities).

**Improvements** 📈

* You can now specify a custom role as the default role for new users

**Bug fixes** 🐛

* We’ve fixed a bug with teams not auto-archiving when their corresponding YAML file is deleted

**January 9, 2024**

**GitOps for services and resources:** We’ve decoupled the toggles for services and resources. You’ll be able to have GitOps enabled for one or the other based on your preferences.

**Initiative notifications for teams:** After an initiative is created, we’ll notify the Slack channels for any teams that own entities that are part of the initiative.

**Improvements** 📈

* We’ve added [auto-mapping for the Wiz integration based on project names](https://docs.cortex.io/docs/reference/integrations/wiz.md#discovery)
* Users, allowlists, and secrets now appear in audit logs
* We’ve added support for importing resources of type AWS::EKS::AddOn and AWS::EKS::FargateProfile from AWS
* GitOps logs now contain links for the GitLab repo and commit

**Bug fixes** 🐛

* When editing ownership, you will no longer see duplicate teams in the dropdown
* Catalog search once again includes archived entities when relevant
* Scorecard filters for a team are now properly applied when navigating to it from the team page
* Attempting to load the Scorecard scores for an entity with no scores from that Scorecard no longer results in an infinite loading state
* We’ve fixed an issue with creating teams from GitLab and ServiceNow in the public API
* The entity type is now properly parsed in entity YAMLs
* If you have Eng Intelligence enabled, the side panel now hides & orders metrics based on Settings configuration
* We’ve fixed rate limit and timeout issues with the LaunchDarkly and PagerDuty integrations
* Signed-out users are once again properly redirected to the login screen


## Related topics

- [Scorecards as code](https://docs.cortex.io/standardize/scorecards/scorecards-as-code.md)
- [Add custom metrics data point](https://docs.cortex.io/api/rest/custom-metrics/add-custom-metrics-data-point.md)
- [Add custom metrics data points in bulk](https://docs.cortex.io/api/rest/custom-metrics/add-custom-metrics-data-points-in-bulk.md)
