Feature Requests

Teams across the organization have expressed the need for a notification feature tied to scorecards. This feature would trigger alerts when predefined thresholds are exceeded, enabling quicker responses to disruptions and enhancing overall operational efficiency. Context: This requirement emerged as a recurring need across teams. Currently, there is no proactive mechanism to monitor scorecard thresholds, resulting in delayed responses to critical issues. Expected Functionality: Ability to define threshold levels for specific scorecard metrics. Real-time or near real-time notifications when thresholds are breached. Notifications delivered through existing communication channels (e.g., Slack, email, Pager duty). Configurable alert settings to cater to various team requirements. Impact: Faster response times to scorecard disruptions. Increased operational efficiency and collaboration. Reduced risk of missing critical thresholds in performance monitoring. Reduced manual work with automations and manual checks. Request: Please consider prioritizing this feature in upcoming development cycles, as it addresses a critical operational need consistently reported by multiple teams.

we are Integrating Dynatrace with IDP components so we need components list in dropdown for particular loggedin user in template UI to select particular component to update, for that we only show them list of componets which has user permission to update not all components list.

Currently the Git Clone step suppprts using a connector with GitHub using GitHub App authentication. The Direct push only supports using username and password and not GitHub App auth.

We kindly request the implementation of the Kubelog plugin for our IDP instance. This plugin will significantly enhance our ability to monitor and manage Kubernetes resources directly within IDP. Plugin Details: Name: Kubelog Plugin Purpose: Viewing Kubernetes logs and performing basic operations within Backstage Key Features: Browse Kubernetes logs of entities directly in Backstage Restart pods from the Backstage interface (available in version 0.9 and above) Integration with Kwirth for log exporting Benefits: Streamlined log viewing for developers Reduced complexity in managing Kubernetes resources Improved self-service capabilities for development teams We appreciate your assistance in implementing this plugin to enhance our IDP functionality and Kubernetes management capabilities

Currently we are able to pull out org or project details in IDP, but a capability to select repo's based on a project would be more helpful for couple of self-services.

Currently, when a pipeline triggered via the Internal Development Portal fails, the only output the user is met with is "Pipeline Failed!". The user needs to see more meaningful logs to be able to understand why a pipeline failed. Especially if that user does not have access to the underlying pipeline.

We would like to have a plugin to integrate Ardoq into IDP to show relationship data in a UI card/tab. Ardoq is our source-of-truth for technology portfolio management and ownership information is already documented there. It would save us time if we could export and render this info in a view like the Catalog graph for entity relations.

We would like to have the same functionality as seen in the Pagerduty plugin for xMatters, which is the service reliability platform we use.

The left nav on the new workflows screen does not play nicely with longer named groups, this should be resizable and ideally you should be able to shrink to maximize screen real estate.

Trying to output an error message to the Internal Developer Portal (IDP) execution view if pipeline fails. It shows the output message only if the pipeline succeeds but unable to do so for explicit pipeline failure.