JSON Fields Not Exported Correctly When Using Export API
FeatureEngineCRUD
#1 — api inconsistency and errors cluster
Bad Request Error API Output is not Consistent with Actual Error
BugPostgresCoreCRUDLow ImpactMed Reach
Unable to default string input to empty string
BugStudioCRUDLow ReachLow Impact
Decimal/Float Fields Validation Throws Misleading Error With Wrong Field Name
BugPostgresEngineCRUDMed ImpactMed Reach
#2 — graphql translation errors cluster
Using translation the variable $t partially works for Field Name Translations
ImprovementStudioUX / DX
AccordionGroup in Translations is not rendered nicely
ImprovementStudioUX / DXLow ImpactMed Reach
GraphQL filter error in Insights panel for M2A relationship
BugGraphQLStudioUXMed ImpactMed Reach
#3 — undefined issues cluster
503 is not appropriate for permission issues when writing files?
ImprovementGood First IssueEngineAssets / FilesLow ReachLow Impact
Style Issues caused by RTL
BugHelp WantedLow ReachHigh Impact
Figure out localization for Kurdish region
ImprovementGood First IssueHelp Wanted
Can’t promote version — Invalid time value
BugRegressionVersioningEngineMed ImpactMed Reach
#4 — directus sdk issues cluster
SDK defaults to any in Schema generic, causing problems
ImprovementSDKLow ReachLow Impact
[SDK] Custom endpoint doesn't work
ImprovementSDKMed ImpactMed Reach
latest directus (11.12.0) has deprecated dependencies
Low ReachLow ImpactDependency
#5 — many-to-many mismatches cluster
[BUG]: foreign_key schema meta missing on m2o fields with unique constraint (MySql8)
BugData ModelingMySQLEngine
Save as copy doesn't duplicate relational items
ImprovementData ModelingStudioMed ImpactMed Reach
Creating multiple `o2m` realationships to the same FK should be forbidden
BugData ModelingEngineMed ImpactLow Reach
Can't distinguish between relational fields on relation interface and display
ImprovementStudioUX / DXLow ImpactMed Reach
#6 — undefined errors and 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
slow query for revisions
ImprovementVersioningPostgresEnginePerformance
#7 — m2a interface issues cluster
Reordering M2A items in versions causes duplication
BugVersioningStudioMed ImpactMed Reach
Scrollbar missing in M2A Related Collections
BugStudioUX / DXLow ReachLow Impact
Save as Copy doesn't duplicate M2A junction item for related items after 11.13.4
StudioContent Workflow
M2A Relation Display Not Showing Properly
BugHelp WantedStudioUX / DXMed ImpactLow Reach
#8 — directus permissions issues cluster
Field Permissions does not have a Copy Raw Value option
ImprovementStudio
Display & Interface fails if it includes fields a user doesn't have permissions to
BugHigh ImpactMed Reach
$thumbnail Field in directus_files Breaks JSON Export Due to Permission/Schema Conflicts
BugGood First IssueHelp WantedStudioAssets / FilesLow ReachLow Impact
Permission conditions are checked against the main object instead of the versioned object being edited
BugRegressionPermissionsStudioMed ImpactMed Reach
#9 — ui inconsistencies and errors cluster
APP: Inconsistent and Extra API calls when initializing, navigating route /content/:collection and navigating Bookmarks
BugGood First IssueHelp WantedPerformanceMed ImpactHigh Reach
Checkboxes custom value support is faulty
BugStudioLow ImpactMed Reach
Item detail page does not keep context
ImprovementStudioUX / DXMed ImpactHigh Reach
Optional Drawer View for Item Details
FeatureStudioUX / DXMed ImpactHigh Reach