Feature Requests

need to merge two services into single service using override values to differentiate them Our automation expects single service here need some guidance here

Segregation of CI and CD pipelines for easy maintenance and better readability. Folder structure for maintaining CI and CD pipelines based on services or tech stack.

We would like a method to be able to define the notification personnel based on an input or expression. This is so that we can utilize an inputset to change what teams are notified for a pipeline template, depending on where it is used. We utilize the same pipeline template across may teams, and need notifications to go to different teams, depending on where the pipeline is being used. RIght now, the value is "hard coded" so we cannot have the notifications go to different teams.

I want to create a local admin account that can bypass Azure authentication, especially useful if Azure is down. This account should not require an email, similar to a service account, to avoid the need for monitoring or logging into an email. It would be beneficial to have this feature to ensure access even when Azure is unavailable.

The banner on harness UI comes by default with dismissible option. Since one of our banner is highly important. There shouldn't be any way that it can get dismissed by user

I would like to have the ability to impersonate a user based on their role. Currently, the role assigned to a user is automatically used during impersonation, and there is no option to change it. It would be beneficial to have a feature that allows selecting a specific role for impersonation to facilitate testing and management.

When using the impersonation feature, an email notification is sent to the user being impersonated. This can be annoying for users who are approving pipelines. It would be helpful to have an option to disable this email notification to streamline the approval process.

We are building various nuget packages using the Microsoft .Net 6.0,7.0 and 8.0. The package is pushed via JFrog connector that doesn't contain the nuget build info. This is a critical requirement for the Jfrog Xray SCA scan. Here are the build info details that provided by the JFrog. We need to pass along the build info while running and uploading to Artifactory. Build info is JFrog source to identify dependencies. Xray will request for the build-info, which contains the list of artifacts and dependencies to scan. Using this information, whatever the build info is able to pick up during the build process, Xray can attempt to match "transitive dependencies" and include it in the analysis. You can find more information on it below: https://www.buildinfo.org/ And an npm/donet example of build passing the build info: https://github.com/jfrog/project-examples/tree/master/npm-example https://github.com/jfrog/project-examples/tree/master/msbuild-example

We need a overview dashboard to globally follow the usage of our template at Account scope in project pipelines.

Hi team, Last time we have checked with you for uploading files during the time of pipeline execution, we were recommended to use the uploadFiles step under custom stage. Upon checking, we were informed that the files uploaded using the step will remain for 37 days and post that they will automatically be deleted and users cannot remove them. We would like to request for a feature where users can delete / remove the files as well. Can you please let us know if this feature can be implemented? Thank you