Feature Requests

I previously raised request #98988 regarding an integration issue with JFrog in Harness Components, where I provided all necessary details along with screenshots (Artifact URL, type). However, after submitting this information, it took longer than expected to receive a response. When I did hear back, I was informed that Harness currently supports only Maven artifacts, which was disappointing. I believe this information should have been clarified earlier in the process, either initially or during the information-gathering phase. With that said, I'm now submitting this as a formal feature request. We are seeking support for additional artifact types, specifically: Generic NuGet Docker Could you please provide an estimate of when this feature might be available or if there’s a timeline for its inclusion in future releases? Thank you for your attention to this request. I look forward to your response.

The following data appears within the Feature Flag Integrations tab when connected with Azure DevOps: Work item, Assignee, Work item status. The problem we have is that there is no differentiation between work item types, such as Features, User Stories, Bugs. We would also like the ability to include additional columns, Priority is the most important one. This is because we may release the feature once all priority 1 and 2 items are complete and we're happy for priority 3 and 4 items to come later, or the rules we use for releasing may depend upon the priorities completed.

Currently I can sort A-Z/Z-A, but it would be much more useful to be able to sort by date created (up/down), so that I can address the oldest tickets, or so I can see the most recent tickets to make sure they're set up properly.

Add "domain" as an available attribute option in the "Bucket targets by" dropdown for percentage rollout variations in Feature Flags. Current Behavior: The percentage rollout feature currently supports bucketing by the following target attributes: Identifier (default) Name location These options appear in: The "Bucket targets by" dropdown in the flag variation configuration The Target Group Criteria modal when defining targeting rules Desired Behavior: Add "domain" as an additional bucketing option alongside the existing attributes (Identifier, Name, location). Use Case: Many organizations structure their targeting based on domain/tenant identifiers, especially in multi-tenant SaaS applications. Being able to bucket by domain would enable: Consistent Feature Distribution Across Tenants: Ensure all users within a specific domain/tenant receive the same variation, which is critical for B2B SaaS applications where feature consistency within an organization is important. Domain-Level Progressive Rollouts: Gradually roll out features to different customer domains/organizations rather than individual users, reducing risk and simplifying rollback scenarios. Better Alignment with Business Structure: Many enterprise customers are organized by domain/tenant, making this a more natural bucketing dimension than individual user identifiers. Example Scenario: A SaaS platform wants to roll out a new dashboard feature to 30% of customer organizations (domains) rather than 30% of individual users. With domain-based bucketing, all users within selected domains would see the new feature, while all users in other domains would see the existing version. Benefits: More flexible targeting options for multi-tenant applications Better control over feature consistency within organizations Reduced complexity in managing feature rollouts for B2B scenarios Improved customer experience by ensuring organizational consistency

We would like the ff-python-server-sdk to support registering for lifecycle events such as READY, FAILED, and CHANGED, similar to the capabilities available in the ff-node-server-sdk. We rely on these events to dynamically adjust runtime behavior—for example, changing log levels on the fly—without requiring a pod restart.

Hi team, this is ticket is part question/part feature request. we have many feature flags stored in "Feature flags" project and we are planning to enable git sync for them. however, we realized that 1 project can only be synced to a single yaml file, which results in a massive yaml file that can be difficult to maintain. we are wondering if the git sync allow wild card matching to pull all yaml files within a folder (ideally separated by teams) to allow easier management. thanks!

Customers need the ability to toggle on features based on dates and time ranges. Example -- turn on FeatureA for customers that created an account between 12/1/2022 and 12/1/2023 -- turn on FeatureB for customers that created an account in 2024. Please vote for this feature and add any additional use cases and requirements if this would benefit you! Thanks, Matt Schillerstrom Harness FF Product Manager

I want to synchronize feature flags across environments in Harness. While I understand the importance of having independent states for each environment, there should still be a way to synchronize feature flags when needed. Independence at creation time is crucial, but as users, we often need to synchronize flags to replicate environments accurately. Currently, there is no way to do this, which creates a significant bottleneck

Presented the Gainsight Dashboard and Aaron saw it as a good starting point for operational visibility, but not yet actionable enough for adoption analytics or leadership reporting. Complete feedback: What was well-received Provides a high-level view of Feature Flags usage in the environment Helps identify old or inactive flags and cleanup opportunities Useful baseline metrics such as: Flags and MTKs utilization FME Usage FME Feature Usage Active flags overview Primary gaps identified Lack of team-level, service or project-level segmentation (project name only available in the Active Flags table but can not show it overtime in a graph) Hard to extract strategic insights or support storytelling of adoption Limited value for executive reporting or proving expansion benefits Access is not frictionless (must open from email link each time) Very limited flexibility for customization or deeper drill-downs

Please enable feature flag CI_ENABLE_MULTILINE_OUTPUTS_SECRETS on our UAT instance: URL： https://ssc-corp-uat.harness.io AccountId: jQZAkmqvQtu77O7qI_uz-Q Name: StateStreet-UAT