add policy name to conditions

[JadeCara]

Ticket ENG-2185

Description Of Changes

Updated the selector to use key with name label for policy conditions

Code Changes

• clients/admin-ui/src/features/integrations/configure-tasks/utils.ts - update to use key
• clients/admin-ui/src/features/integrations/configure-tasks/components/ConditionValueSelector.tsx - update selector

Steps to Confirm

1. Verify that name any key show up under policy

2. Create a consent manual task with condition and verify it works as expected

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • All UX related changes have been reviewed by a designer
  • No UX review needed
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	Jan 14, 2026 6:29pm

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
fides-privacy-center	Ignored		Jan 14, 2026 6:29pm

[greptile-apps]

Greptile Summary

Added privacy_request.policy.name and privacy_request.policy.key to the allowlist of available condition fields for manual tasks.

• Both fields are string types and will be handled correctly by the existing field type detection logic
• Test coverage already exists for these fields in the test suite
• These fields follow the same pattern as other policy fields (privacy_request.policy.id, privacy_request.policy.has_access_rule, etc.)

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change adds two new string fields (privacy_request.policy.name and privacy_request.policy.key) to an existing allowlist. The fields already have test coverage, follow the same pattern as existing policy fields, and will default to "string" type in getFieldType() which is correct for these fields
• No files require special attention

Important Files Changed

Filename	Overview
clients/admin-ui/src/features/integrations/configure-tasks/utils.ts	Added privacy_request.policy.name and privacy_request.policy.key to the allowed privacy request fields list for manual task conditions