Feature Requests

We have set up user groups to receive notifications in the Microsoft Teams channel when approvals are required. However, it is currently not possible to approve requests directly within the Teams channel. Raising this feature request to enable approval actions via the Teams channel.

We'd like the ability to create environment variables for Azure Function Apps. Currently, the environments are only made available in the delegate container and don't get propagated to Azure.

Basically, In CI Pipelines we observe that the test results will be published to the Tests tab. Likewise, we need to have the same for CD Pipeline also. But in one of the CD pipeline I'm unable to publish the test results to the Tests tab even after using right plugin. Enable the right feature request to publish the test results (Ex: JUnit XML from .NET Smoke Tests) in Tests tab of CD pipelines.

Make org-scoped environments discoverable in Environment Tab(currently project-level environment) views to reduce friction and improve developer UX.

Increase visibility of (failed) kubernetes deployments. Harness could show relevant sections from a configurable log provider (ex Opensearch) during deployments (or optionally only during deployment failures). A common scenario for us is where a deployment fails due to the container not starting. Currently this will only show up as a timeout in the harness deployment view. Then the developer has to go to the log provider and use various filters to find the logs for the deployment in question. If there instead was a section for logs (fetched from a configurable log provider, it would likely be easier for developers to find the root cause of a failed deployment.

Current WinRM credential configuration is limited to a single server, as it relies on a fixed ComputerName and ConfigurationName. This restricts remote PowerShell execution to only the specified host. To support scalable automation across multiple servers, the WinRM credential setup needs to be extended to dynamically target different hosts, enabling broader compatibility and centralized management.

We would like Terraform Provider to allow for the same Splunk connection/authentication types. We can set other authentication methods in the UI, but do not have a method for how to do this within Terraform Provider

Harness' autocreation documentation states that resources should be created in specific/designated folders however, the Harness UI does not follow this convention at all. We'd like for Harness to use these default paths or allow us to configure these default paths per resource since the autocreation paths used for pipelines, environments, services, etc will be different.

Please reference: https://support.harness.io/hc/en-us/requests/90306 Support ticket 90306 for this issue When using an Org Parent Pipeline Template, if the child template in a Harness project switches template version from say, v0.0.1 to v0.0.2, Harness seems to switch branches to look for that template in a different branch (the default one) instead of the branch stored on the Parent Pipeline. This used to work when switching, but something changed recently. Can you fix it such that it looks for the branch on the Parent Pipeline where the original pipeline is stored?

The idea is to preload additional context about custom configurations such as: connectors templates initTimeout CI infrastructure using KubernetesDirect (as an example) honor active OPA policies this additional context will make interactions with AI DevOPs agent slightly easier since this additional context will be remembered among sessions. To provide an example, Copilot provides a similar feature described below. Clearly, it won't be identical in the context of Harness, but it illustrates well the intention of the request to remember basic settings among interactions with the AI DevOps Agent. https://docs.github.com/en/copilot/how-tos/custom-instructions/adding-repository-custom-instructions-for-github-copilot