The biggest theme for our first 2024 summer release notes is using the portal for engineering insights. Portals are a natural place to understand everything about the engineering organization: its productivity, agility and standards compliance. This is a result of the fact that the portal is a single source of truth about teams, developers, services and infrastructure and the relationships between them. This new software engineering intelligence capability makes Port more useful to engineering leaders, especially since Port doesn’t just provide insights, but also the power to change behavior, productivity and standards compliance.
Biggest
Historical data trends - engineering insights
Port now supports tracking and visualization of historical data. This is ideal for a variety of what’s called “software engineering intelligence” needs, such as DORA and other engineering productivity metrics, and also useful for any work on standards compliance. We’re thinking of calling this set of capabilities “insights” 💡. Practically you can use it as a line chart widget that displays the history of number properties as trends. Line charts can also visualize the history of aggregation and calculation properties to create a bird's-eye view of custom metrics, like:
- Tracking engineering metrics
- Following the scorecard passthrough rate
- Open critical vulnerabilities trends, and more
See docs to learn more.
Map GitHub file content to the catalog
Bring GitOps to life with json and yaml mapping, enriching your catalog with any data you already have in your repositories:
1. Use JQ to map specific fields to your catalog entities. For example, map the “package manager” from a package.json file to a service entity
2. Create and update multiple entities based on arrays in files. For example, map all dependencies from a package.json as an entity per dependency
See docs to learn how to map file content from GitHub
Medium
Multiple approvers to self-service actions
You can now require more than one approval for an action to be completed, for cases that require multiple approvals. All approvers will get notified for approval and can add a note explaining their decision. See docs to learn more.
Define relations based on any property
When defining relations as part of integration mapping, you can now define the relation using a comparison with any entity property instead of just the identifier. See docs
View permissions at the API level
You can new enforce view permission for entities according to roles, users, specific teams, or dynamic team ownership, which will take effect both on the Port app and when interacting with the API. See docs
Small
Live examples for JQ and Mapping playgrounds
We added a live examples capability when testing the mapping for K8s, GitHub and BitBucket exporters to make the mapping experience much easier
Mirror properties for many-to-many relationships
Mirror and view multiple related entities and their properties.
Use entity context when triggering automation with the timer expired trigger
You can now use entity details for context when defining automations based on their timer expiration trigger. Learn more on how to use trigger context in automations