Feature Requests

The terminationGracePeriodSeconds is currently hardcoded in the TimescaleDB StatefulSet in the subchart. This makes sense for production installations, but in test instances it causes the deletion to hang unnecessarily until the grace period expires. We would like to be able to override this value in such cases. I have submitted a pull request with exactly the change I mean, which you can either merge or just use as a reference: https://github.com/harness/helm-timescaledb/pull/31 The change should of course be eventually referenced by the main Harness Chart, so that it can be configured on the main Harness values.yaml. Many thanks.

Please expand the current search capabilities when searching through Organizations, and Projects. Please add the ability to search for pipelines across all projects in all orgs. Some additional search options would be great too: Filtering out Organizations with no Projects Filtering out Projects with no Pipelines Searching on a particular attribute for an Organization or Project - not just identifier or name Thanks

Description: Currently, in Looker dashboards, each environment grouping based on (DEV, QA, UAT, PreProd, Prod, etc.) is can't be displayed as an independent column. While custom dimensions allow us to partially meet the use case by listing service–artifact versions along with environment names, Looker does not support grouping multiple environments together or creating a consolidated entry that represents service details across an environment group. Expected Enhancement: Ability to define environment groups (e.g., Non-Prod, Prod, Special-Prod). Ability to group environment columns in Looker dashboards based on these definitions. Support for displaying aggregated or consolidated service details (such as artifact version or deployment status) at the environment-group level.

We would like it if fast fail could be applied to approval and verification steps in pipelines. Often, in non-microservice deployments, we deploy services in parallel and we may be verifying or waiting for approval on one service; in the event that the approval for the service is rejected, the pipeline as a whole should be rejected as quickly as possible and rollback initiated.

It would be useful to create shareable dashboards that can be used by several users customized based on their user. Use case would be something that could track all relevant builds to their username in the last 30 days.

Requesting Harness to add support natively for Pipeline Mean Time to Recovery (MTTR) metric that tracks the duration between a pipeline failure and its subsequent return to a successful state. To be actionable, this feature must move beyond simple averages and support statistical distributions (Median, P75, P90). Native integration of this metric allows us to seamlessly maintain our internal reporting standards without relying on custom workarounds. More importantly, this metric provides a clear lens into developer friction. By visualizing exactly how long teams are blocked from merging, we can pinpoint specific bottlenecks, quantify the cost of interruptions, and systematically accelerate our path to green.

We would like the ability to combine data from multiple explores into a single dashboard tile

We would like to have a single dashboard shared with several users each with their own set of inputs. Right now they have to pick the relevant data from the dropdowns every time they access the dashboard, it would be great if they could save a preset for themselves.

Update the post to get dashboard data api to be able to pull data from a subset of tiles. Use case is that we could have a dashboard with a bunch of tiles and I only want one of those tiles data for an automation.

In dashboards, it would be helpful to copy a tile from one dashboard to another. Use case would be having several people copying a dashboard to their own sandbox folder, creating their changes, and being able to push there changes back to the original dashboard.