directus-extension add modifies dependencies
ImprovementExtensionsExt SDKMed ImpactLow Reach
#1 — directus dependency issues cluster
latest directus (11.12.0) has deprecated dependencies
Low ReachLow ImpactDependency
isolated-vm@5.0.3 not compatible with Node.js 24 (V8 API changes) — build fails on Linux x64
ImprovementChoreDependency
chokidar update to v4 broke extension auto reload
BugExtensibilityEngineMed ImpactHigh Reach
#2 — validation rule inconsistencies cluster
Allow selecting relationship fields on field validation
Bug⚠️ EnterprisePermissionsStudio
Error when saving entry with validation rule
BugValidationEngineMed ImpactMed Reach
Field Permissions does not have a Copy Raw Value option
ImprovementStudio
Group-level conditional required validation not enforced on child fields when group is shown; required triggers even when hidden (2 bugs)
BugValidationStudioLow ReachHigh Impact
#3 — broken features and functionality cluster
Bug report: Vue components in Operation Extension broken
BugGood First IssueStudioExtensionsLow Reach
`private-view` split view slot feature missing
BugStudioExtensionsMed ImpactMed Reach
VListItem with clickable prop renders invalid html
StudioMed ImpactMed ReachTask
[SDK] Custom endpoint doesn't work
ImprovementSDKMed ImpactMed Reach
[app] UX feature: Shift+Click row selection in tables
ImprovementStudioLow ReachLow Impact
#4 — m2m/m2a duplication and functionality issues cluster
Save as copy doesn't duplicate relational items
ImprovementData ModelingStudioMed ImpactMed Reach
Reordering M2A items in versions causes duplication
BugVersioningStudioMed ImpactMed Reach
Save as Copy doesn't duplicate M2A junction item for related items after 11.13.4
StudioContent Workflow
create related item with "empty" or default state
BugStudioMed ImpactMed Reach
#5 — schema operations performance cluster
v11.10.0 snapshot changes makes schema apply try to add an existing table/existing columns
BugRegressionData ModelingEngineMed ImpactMed Reach
Activity Log Not Created When Updating Field Schema
BugEngineLogsMed ImpactMed Reach
API: Content Version accountability records created even if collection is set to not track anything
BugEngineLogsLow ImpactMed Reach
#6 — permission conflicts and limitations cluster
Display & Interface fails if it includes fields a user doesn't have permissions to
BugHigh ImpactMed Reach
SDK types still reflect the old permission system
BugSDKMed ImpactMed Reach
Deleting field doesn't deletes field from permission
BugPermissionsEngineMed ImpactMed Reach
$thumbnail Field in directus_files Breaks JSON Export Due to Permission/Schema Conflicts
BugGood First IssueHelp WantedStudioAssets / FilesLow ReachLow Impact
#7 — sdk type safety issues cluster
SDK defaults to any in Schema generic, causing problems
ImprovementSDKLow ReachLow Impact
Checkboxes custom value support is faulty
BugStudioLow ImpactMed Reach
#8 — undefined issues in directus plugins cluster
Style Issues caused by RTL
BugHelp WantedLow ReachHigh Impact
AI chat doesn't work when Directus PUBLIC_URL have path
BugStudioMed ImpactLow ReachAI/MCP
Avatar/logo flashing issues occur again on page changes.
BugStudioUX / DXLow ImpactMed Reach
Save as copy not working, just spins with no requests sent.
BugStudioCRUDLow ReachLow Impact
#9 — error in field handling cluster
Decimal/Float Fields Validation Throws Misleading Error With Wrong Field Name
BugPostgresEngineCRUDMed ImpactMed Reach
Bad Request Error API Output is not Consistent with Actual Error
BugPostgresCoreCRUDLow ImpactMed Reach
CockroachDB integer overflow
BugCockroachDBEngineCRUDMed ImpactLow Reach
#10 — creating new collection validation issues cluster
Creating New Collection -> Optional Fields -> Saving Custom Field Names
ImprovementData ModelingStudioLow ImpactMed Reach
Creating New Collection -> Add validation as user types
ImprovementData ModelingStudioMed ImpactMed Reach
Creating New Collection -> Optional Fields -> Add Select All
ImprovementStudioCRUDLow ImpactMed Reach