\r\n \u003C/div>\r\n\u003C/transition-expand>\r\n```\n\n### To Reproduce\n\n1. Create a custom interface that manages state (e.g., a file upload interface)\r\n2. Add this interface to a field in your collection schema\r\n3. Place this field within a Group interface (using an alias field with the Group interface)\r\n4. Open an item in the collection\r\n5. Your custom interface loads normally within the group\r\n6. Collapse the group\r\n7. Expand the group again\n\n### Directus Version\n\n11.1.1\n\n### Hosting Strategy\n\nSelf-Hosted (Docker Image)\n\n### Database\n\nPostgreSQL 16",[3042,3045,3047,3048,3050],{"name":3043,"color":3044},"Improvement","c2e0c6",{"name":3046,"color":3029},"S3",{"name":3022,"color":3023},{"name":3049,"color":3026},"CRUD",{"name":3051,"color":3029},"I3",24303,"Directus Group Interface Unmounting Child Components Bug","2025-04-21T17:52:56Z","https://github.com/directus/directus/issues/24303",0.6435926,{"description":3058,"labels":3059,"number":3062,"owner":3033,"repository":3033,"state":3034,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### Describe the Bug\n\nWhen creating an item from a side of the m2m relation. The fields field of the relation can be set to itself, and this creates a duplication in the m2m table.\r\n\r\nIt would be better when creating a new entry from the related table if the current item was already selected in the interface, so the user would not re-select it and so creating a duplicate. In older versions, the field was not editable, so this couldn't happen.\n\n### To Reproduce\n\n1. Create two collections.\r\n2. Create m2m connecting both collections with relation fields in both collections.\r\n3. Create an entry in each collection.\r\n4. Open one of the created entries.\r\n5. From the relation field, use \"Create new\"\r\n6. Create a new item and in the relational field select the item from which you started the \"Create new\" action.\r\n7. Save and it duplicates the relation.\r\n[issue.webm](https://github.com/directus/directus/assets/7550391/44bfb052-9c37-46ec-979f-513329cad8f3)\r\n\n\n### Directus Version\n\nv10.6.1\n\n### Hosting Strategy\n\nSelf-Hosted (Docker Image)",[3060,3061],{"name":3019,"color":3020},{"name":3022,"color":3023},19717,"M2M duplicating relation when creating item from related item","2025-03-21T12:10:02Z","https://github.com/directus/directus/issues/19717",0.6640914,{"description":3068,"labels":3069,"number":3070,"owner":3033,"repository":3033,"state":3071,"title":3072,"updated_at":3073,"url":3074,"score":3075},"",[],19920,"closed","Add GraphQL version parameter","2024-02-01T01:25:53Z","https://github.com/directus/directus/issues/19920",0.6083899,{"description":3077,"labels":3078,"number":3082,"owner":3033,"repository":3033,"state":3071,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Describe the Improvement\r\n\r\nOutput type of the `readItem` or similar commands is hardly readable in the IDE. Take a look at this example:\r\n\r\n```typescript\r\nimport { type CompleteSchema, type DirectusUser, createDirectus, rest, readItem } from \"@directus/sdk\";\r\n\r\ntype TestEntity = {\r\n id: string;\r\n user: DirectusUser\u003CSchema>;\r\n name: string;\r\n nickname: string | undefined;\r\n};\r\n\r\ntype Schema = CompleteSchema\u003C{\r\n testEntity: TestEntity[] ;\r\n}>;\r\n\r\nconst client = createDirectus\u003CSchema>(\"\").with(rest());\r\n\r\nconst data = await client.request(readItem(\"testEntity\", \"1\", {\r\n fields: [\"id\", \"nickname\", { user: [\"id\"] }]\r\n}));\r\n```\r\n\r\nIf I hover over the `data` variable to see the type, VSCode will show me this:\r\n\r\n\u003Cimg width=\"570\" alt=\"image\" src=\"https://github.com/user-attachments/assets/b6b2eb7d-374e-46b1-8762-1d8d10876bdd\">\r\n\r\nThere is a way to improve DX by \"prettifying\" complex types by leveraging a saving of \"computed\" type via TS mapping types (see this article for details: https://www.totaltypescript.com/concepts/the-prettify-helper).\r\n\r\nI've already implemented this in my fork of Directus (see [commit](https://github.com/directus/directus/pull/23494/commits/c521ec4a9239ac30bf0ee9a55681b61731e5f21e)) and here what I got for the same code snippet:\r\n\u003Cimg width=\"489\" alt=\"image\" src=\"https://github.com/user-attachments/assets/dea63851-f641-44ae-81a0-0873e9cdfb41\">\r\n\r\nI think this change might improve DX without any drawbacks and also simplify usage of type aliases to stay in sync with actual data shape that we get from the API when using `fields` in the query of a command. \r\n",[3079,3080],{"name":3043,"color":3044},{"name":3081,"color":3023},"SDK",23493,"SDK: prettify rest command output type in IDE","2024-11-25T23:11:54Z","https://github.com/directus/directus/issues/23493",0.6384528,{"description":3088,"labels":3089,"number":3090,"owner":3033,"repository":3033,"state":3071,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Describe the Bug\n\nI am using Directus version 10.3.0, and overall, everything is working well. However, I am facing an issue where I am unable to retrieve information about the clients currently connected to the WebSocket. After inspecting the code, I noticed that the WebSocketService provides a \"clients\" method for this purpose.\r\n\r\nHowever, when I attempted to construct an endpoint and looked for the WebSocketService in the services, I couldn't find it. I am using create-directus-extension with a version of 10.0.5.\r\n\r\nCould you please assist me in resolving this issue and guide me on how to retrieve the information about connected WebSocket clients in Directus version 10.3.0?\r\n\r\nThank you.\n\n### To Reproduce\n\nexport default (router, { services }) => {\r\n console.log(services.WebSocketService); // undefined ??\r\n\trouter.get('/', (req, res) => res.send('Hello, World!'));\r\n};\r\n\n\n### Directus Version\n\nv10.3.0\n\n### Hosting Strategy\n\nSelf-Hosted (Custom)",[],18924,"Unable to retrieve information about currently connected WebSocket clients","2024-02-01T10:02:47Z","https://github.com/directus/directus/issues/18924",0.6393577,{"description":3096,"labels":3097,"number":3098,"owner":3033,"repository":3033,"state":3071,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Describe the Bug\n\nNot able to view the admin page on Firefox and I get the following error message on the console. `Error: Uncaught TypeError: Intl.Segmenter is not a constructor` which shows that the Intl.Segmenter API, used for advanced text segmentation, is not supported in the browse. I am using Debian 12 and the Firefox version is 115.15.0esr (64-bit).\n\n### To Reproduce\n\nJust open Directus using Firefox.\n\n### Directus Version\n\nv11.3.5\n\n### Hosting Strategy\n\nSelf-Hosted (Docker Image)\n\n### Database\n\n_No response_",[],24404,"Page is stuck on loading when using firefox due to Intl.Segmenter not being supported on the borwser","2025-02-13T16:33:05Z","https://github.com/directus/directus/issues/24404",0.6453566,{"description":3104,"labels":3105,"number":3106,"owner":3033,"repository":3033,"state":3071,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Describe the Bug\n\nCannot delete fields\n\n### To Reproduce\n\nDelete a field of a collection in data model\n\n### Errors Shown\n\n\n\n### What version of Directus are you using?\n\n9.15.0\n\n### What version of Node.js are you using?\n\ndont know\n\n### What database are you using?\n\nPostgres 12\n\n### What browser are you using?\n\nChrome\n\n### How are you deploying Directus?\n\nDocker",[],14865,"Cannot delete a field in data model","2024-02-02T09:03:14Z","https://github.com/directus/directus/issues/14865",0.6480145,{"description":3112,"labels":3113,"number":3114,"owner":3033,"repository":3033,"state":3071,"title":3115,"updated_at":3116,"url":3117,"score":3118},"Add docs for focal points (#20838)",[],20895,"Add docs for focal points","2024-03-18T02:32:39Z","https://github.com/directus/directus/issues/20895",0.6484484,{"description":3120,"labels":3121,"number":3122,"owner":3033,"repository":3033,"state":3071,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### Describe the Bug\n\nwhen Directus is launched directly via Node.js or with PM2 in a single instance, the CPU usage remains relatively low, ranging from 0.2% to 2%. However, when running Directus with PM2 in cluster and fork modes, the CPU usage spikes significantly, reaching levels between 100% and 150%.\r\n\r\nDirectus v10.2.1\r\nHosted: Self via CLI\r\nOS: Rocky Linux\r\nPM2: v5.3.0\n\n### To Reproduce\n\n# PM2 Config\r\n\r\n```\r\nmodule.exports = {\r\n apps: [\r\n {\r\n name: \"crm\",\r\n script: \"npx\",\r\n args: \"directus start\",\r\n restart_delay: 500,\r\n instances: 10,\r\n max_memory_restart: \"1G\",\r\n },\r\n ],\r\n};\r\n```\r\n\r\n# PM2 1 INSTANCE\r\n\r\n\r\n\r\n# PM2 10 INSTANCES\r\n\r\n\r\n\r\n\r\n\r\nI thought maybe it's a initializing issue so I waited 1 hour and it's looks the same\n\n### Directus Version\n\nv10.2.1\n\n### Hosting Strategy\n\nSelf-Hosted (Custom)",[],18771,"High CPU usage when running in Cluster & Fork modes with PM2","2024-02-01T08:03:35Z","https://github.com/directus/directus/issues/18771",0.6500578,["Reactive",3128],{},["Set"],["ShallowReactive",3131],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fvGTP6RXWL2t8VWp4h10csPfhMSp4YMR5s9U6o4TdzMY":-1},"/directus/directus/22686"]