harness - The Modern Software Delivery Platform®
Create
Log in
Home
Feedback
Feature Requests
Log in to your harness - The Modern Software Delivery Platform® account to give feedback
Log In
Boards
Feature Requests
Powered by Canny
Feature Requests
Anonymous
Feature Requests for Harness. Select 'Category' based on the module you are requesting the feature for.
Details
Category
Select a category
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Planned
In Progress
This Fiscal Quarter
Next Fiscal Quarter
Long-term
Pending Feedback
Complete
posts in
All Categories
All Categories
Continuous Delivery & GitOps (1,769)
Continuous Integration (389)
Feature Mgmt & Experimentation (291)
Cloud Cost Management (220)
Feature Flags (102)
Service Reliability Management (10)
Security Testing Orchestration (101)
Chaos Engineering (38)
Software Engineering Insights (117)
General Platform Requests (458)
Internal Developer Portal (120)
Code Repository (42)
IACM (36)
Continuous Error Tracking (13)
Drone 2.x (13)
Open Source (31)
SSCA (13)
Database DevOps (14)
Application and API Posture (0)
Application and API Security (1)
Application and API Protection (0)
Traceable Platform (1)
Increase the duration of Assume Role session in AWS Connector
With an AWS connector set as assume role on delegate, the role has by default a timeout of 15 mins. There is a need to increase this timeout from the default of 15 min to a larger amount, say 1 hr. This is supported using an awscli command, where the duration for assume role session can be defined. Same ability to define this in the connector for assume role on delegate is needed.
2
·
in progress
4
To support expression as part of allowed values of a runtime input
Currently, only fixed values are supported as allowed values of a runtime input. The idea is to populate a list of values in one step that could be used in the later step as the execution runtime input allowed values. Then, the end user could have the option to choose those allowed values that populated from the previous step as part of the execution runtime input.
11
·
in progress
22
Implement column on Template list GUI page to show if referenced and ability to filter by this
Currently the Account Template page does not show if a Template is referenced by any pipelines. This means to determine if a Template is in use or referenced, we have to drill into each individual template to view. Having the ability to view this at the list level, as well as the ability to filter by this, would be a massive time saver.
2
·
in progress
6
Add Timezone support for Cron Triggers
Cron triggers run off of UTC, with no support for local time (and therefore no support for DST). In locations which use DST, this results in the local time of a job's execution shifting twice per year without manual intervention
6
·
in progress
21
Stage Grouping
It would be nice if we had an option for stage grouping similar to step groups. The thought is if a pipeline has selective stages enabled when i click run, I could check a group of stages to run vs having to select a ton of check boxes
11
·
in progress
26
Support User Group For Email Step
FIS global has requested to support user group in E-Mail Step. This will help them to provide the user group for sending E-mails instead of manually adding all the users.
3
·
in progress
31
Support Vault OIDC Connector for IaCM Workspaces
We request support for the Vault OIDC connector in IaCM workspaces in Harness. Currently, the Vault connector cannot be used within IaCM, limiting secure and centralized secrets management.
3
·
in progress
7
How to hide the script being displayed in the execution logs
While executing the pipeline, how to hide the code/script being displayed in the execution logs.
9
·
in progress
11
Requesting a report to view the templates used with specific version.
We would like to have a report that shows templates (step, stage, and pipeline) used in pipelines with versions of those templates. This is to make sure I have a view of templates used and plan for upgrade appropriately.
5
·
in progress
8
Make gitconfig available for policy evaluation for all entities that can have git manifest
Currently only for pipeline entities, gitconfig is available for policy evaluation. The feature request is to make this available for all entities backed by git manifest. This will allow use cases such as "disabling direct commits to main branch" or allowing pushes only on feature or release branches.
3
·
in progress
4
Load More
→
Powered by Canny