Weiko

## Scope & Context Some queries are quite expensive and we currently have no way to create an index for our standard objects except for FK. Ideally we should be...

## Scope & Context Currently, all relations have "ON CASCADE DELETE" by default. This causes some issues for certain objects. Ideally we would like to define this individually for each...

ObjectMetadata decorator have an imageIdentifier properties

8

## Scope & Context Identifiers are used by some client components to represent a record. Those identifiers are mapped to existing field-metadata and the object-metadata table contains both labelIdentifierFieldMetadataId and...

## Scope & Context Each workspace has its own objects and graphql schema, defined through some metadata (objects, fields, relations, ...). If I create an object named "person", I should...

## Bug Description We've renamed the property eventParticipants to calendarEventParticipants within the calendarEvent object, without modifying its standard-id but the workspace sync failed. ``` Sync of standard objects failed with:...

Enforce field-metadata options field to have UPPERCASE values for standard objects

1

## Scope & Context Enforce field-metadata options field to have UPPERCASE values ## Technical inputs Probably in the FieldMetadata decorator. If options is provided, try to uppercase their values and...

- Check broken connection / wrong credentials - Check relations - Check app (show page, list, etc)

Product issue https://github.com/twentyhq/twenty/issues/4986 Find a way to implement many to many relationship, first candidate will be activities and will be implemented in a later ticket

A search bar has been introduced in the filter dropdown menu however we don't want to apply debounce since the search has no side-effect and is purely FE (it's not...