This work aims to add a method to DevCycle that will notify users of the platform when Features are in a state of their lifecycle where they can be marked as 'permanent' or have their variables cleaned up from the code.

When using SCIM/SAML account provisioning with permissions turned on you will now be able to manage access and roles on a per-project basis.

Ensure all DevCycle SDKs have an OpenFeature provider built-in. This project will focus solely on upgrading our current support to match what’s available in OpenFeature.

The ability to define your own custom Feature Type & Template, vs using the existing four Feature options (Release, Experiment, Ops, Permission).

This functionality allows teams to define their Feature statuses, such as In Development, QA, Production, etc., which gives features a more relevant meaning for every team based on their internal processes.

A DevCycle Linear integration streamlines your workflow by enabling the linking of Linear issues directly to features within DevCycle, making the feature status easily viewable within Linear.

This work would be redesigning the feature form into a tabbed view, and ensuring relevant Feature information is easy to find for users and the experience of making Feature updates seamless.

Adding an API endpoint and functionality to the DevCycle SDKs that provide a JSON output for why a specific user received a given Variable value. This project should also ensure that our OpenFeature providers are updated to leverage the new evaluation reason functionality.

A historical lookup of what a given user received at a specific time. This project will create a new section of the DevCycle dashboard where you can inspect users and see what Features, Variations, and Variables they received at a given time.

This work will include adding multi-select filtering, more filtering options, and an overall improved UX so it is easier visualize work and maximize efficiency for team’s overall software delivery process.

Adding a "cover page" to Features in DevCycle that uses a markdown editor with embeddable media so that all users can better understand the purpose of a Feature. (e.g. custom links, JIRA ticket/epic status, description, etc.)

Sub-feature of customizable feature statuses. If X occurs, trigger a status change (e.g., enabled targeting in Staging & added targeting rule using QA audience, change status to QA).

Bi-directional integration with two observability platforms as prototypes, Dynatrace and Sentry. This work will focus on building a way for data to be sent from DevCycle regardless of what your observability platform is.

Contribute back to OpenFeature, a Next.js SDK spec. Once we’ve created the OpenFeature spec, this project will focus on creating an OpenFeature provider built into our Next.js SDK.

Define custom Roles & Permissions for your Organization.

An aggregate view of all Feature Audit Logs for a particular Project.

A realtime feed of user data, feature/variable evaluations and event triggers

Ability to associate your Features' flag values with spikes in your error logs in DataDog.

Bi-directional integration between DevCycle for Audiences and events. Please let us know if Audience syncing or event integration is a higher priority for your team!

Adding the concept of deleting a Variable to the DevCycle interface. Sometimes, users make mistakes with variables and need to clean things up, so they need an easy way to remove unwanted variables completely.

Expand DevCycle's code pipeline integrations to include Azure DevOps.

Creating a client-side C# SDK to augment that server-side C# SDKs.

Adding a Regex Match comparator to DevCycle's targeting rules to enable more complex methods of targeting.

Giving teams the ability to customize what makes a flag stale. Given every team has a different process and timelines for rollouts, each will have different rules that determine when a flag should be cleaned up.

Generate and submit a PR directly from the DevCycle interface for stale Variables and Features.

Download or export a Feature's Audit Log.

Audiences that are not Project-specific but available to be used in all projects within a DevCycle Organization.

Bi-directional integration with Amplitude for the purposes of pulling cohort data into DevCycle and sending Feature inclusion data to Amplitude.

Ability to instruct the SDK to serve certain values while disabling all network activity to the DevCycle servers that could influence the tests.

The ability to exclude users exposed to other Features as part of a Targeting Rule or exclusion group/Audience.

The ability to pause & resume a rollout.

Adding a "cover page" to Features in DevCycle that uses a markdown editor with embeddable media, so that all users can better understand the purpose of a Feature.

Providing the ability to define Variables in code and then push those Variables to the DevCycle dashboard, ensuring that your codebase is the source of truth for Variable definitions.

Allowing DevCycle users to save multiple user IDs (potentially per environment) to a DevCycle Identity for Self-Targeting.

Connect ServiceNow to DevCycle's Approval Workflows so they can be actioned in ServiceNow.

The ability to use multiple events either AND'ed or OR'ed together as the combined conversion events for a given metric.

Create the system and structures by which DevCycle can listen for inbound webhooks and react as necessary. Setting the stage for integrations like one with Datadog, where crossing an SLO turns off a Feature.

Adding to DevCycle the ability to create rules and automations for Feature status changes. Specifically this builds on top of Custom Feature Statuses, to ensure that when a Feature is In Development, In Production, etc it has specific targeting rules set.

Oscar -- HITRUST compliance, we will need this asap

Providing the ability to define Custom Properties in code and then push those Properties to the DevCycle dashboard, ensuring that your codebase is the source of truth for Custom Property definitions.

A DevCycle provider for the Vercel toolbar, which now supports built-in feature flag overrides.

Expand the capability of DevCycle's Code Cleanup functionality by leveraging generative AI.

Add functionality, similar to our Javascript SDK, that triggers a hook when a Variable is evaluated in the mobile SDKs.

Create a generalized integration that supports the OpenTelemetry standard to pass feature flagging data as context for telemetry data.

Create an integration between Asana and DevCycle that creates a bi-directional link between asana and DevCycle, shows off the Feature status within Asana and controls the Feature status remotely.

Create a Gitops style of managing Variable and Targeting changes, so that those changes are approvable and auditable through the traditional Git process.

Improving overall UX when building & managing Audiences throughout the platform.

Create the initial integrations with key CI/CD platforms like CircleCI, Jenkins, etc, enabling the control of flags through CI/CD to validate builds.

This project would result in a publicly available server-side SDK that is built natively for Rust.

After the initial guided onboarding, once a user is dropped into the main dashboard, leveraging a tutorial or tooltips to introduce new users to key DevCycle concepts in a lightweight way.