This PR was created by [GitStart](https://gitstart.com/) to address the
requirements from this ticket:
[TWNTY-7526](https://clients.gitstart.com/twenty/5449/tickets/TWNTY-7526).
---
### Description
We are using standard field and object IDs because there is a problem
when creating them as we would with helpers.
We were creating custom objects and removing them in afterAll, but there
is a problem that causes a conflict in the object IDs if the tests run
at the same time. The solution would be to modify the test command as
mentioned here:
<https://github.com/typeorm/typeorm/issues/6125>
Currently, we are using the standard IDs but we can create the objects
within the test if you want, but we would need to make them run in
sequence
### Demo
### Refs
#7526
---------
Co-authored-by: gitstart-twenty <gitstart-twenty@users.noreply.github.com>
Co-authored-by: Charles Bochet <charles@twenty.com>
Closes#7179
The font color of the button has been set to use
`theme.font.color.danger`. This means that the color will be red
regardless of whether the theme is inverted or not, which was the issue
before.
Merge conflicts have been resolved.
## Context
ObjectMetadataService became quite large and handles too many
responsibilities. I'm trying to refactor a bit this part in preparation
of a larger work that will combine object-metadata services and
sync-metadata logic
- Created a STANDARD_OBJECT_ICONS that can be reused in relation
creation to refer to a standard object icon.
- Created a STANDARD_OBJECT_FIELD_IDS that can be used with an object
name to get its standard field ids.
- Moved migration, record and relation creations to dedicated services,
refactored to improve performances and readability
- Refactored some validation logic
---------
Co-authored-by: Charles Bochet <charles@twenty.com>
Develop a script to facilitate the migration of data from another CRM to
Twenty (750 points)
I had to write a script to add data to HubSpot CRM :)
I wrote migration script to move data from HubSpot --> Twenty.
Here's the GitHub
[Repo](https://github.com/Khaan25/twenty-migration-script) - Video
attached in files
Hope it will be beneficial for people and Twenty Community :)
quest:
create youtube video
points
750
video link
https://youtu.be/qfZyhrhCeyo
task performed:
- I've created a detailed video showcasing Twenty with a walkthrough on
Twenty Dashboard with all it's elements, promoted 3 blogs posts of
Twenty as well
- one with detailed guide on twenty
- one on self hosting twenty
- one for integrating with n8n
- I've also demonstrated the working of n8n integrated workflow towards
the end of video, i hope this shows enough proof to merge #8045
This Pr fix the issue (#8093)
In the oss.gg folder under the no-code-challenge directory, the file
title is incorrect. The current title reads, “Write a self-host guide
blog regarding Twenty CRM,” but the actual task is to “write a blog on
integrating n8n or Zapier marketing tool with Twenty CRM."
Expected behavior
The file title should accurately reflect the actual task to avoid
confusion. It should read: “Write a blog on integrating n8n or Zapier
marketing tool with Twenty CRM."
Example:
• File Path: oss.gg/no-code-challenge/
• Suggested Fix: Update the file title to match the actual task
Points
50
In this PR
1) (FE) fixing update of name not taken into account if toggle value is
changed in the same transaction
2) (BE) moving same nameSingular and namePlural validation before
effective update
#8105
Side Quest: Write a blog post about sharing your experience using Twenty
in a detailed format on any platform. Points: 750 Points Proof: Add your
oss handle and blog link to the list below.
Added My Submission Entry in oss.gg
Create a YouTube video about Twenty (750 points)
I've created a detailed video showcasing Twenty and walkthrough Twenty
Dashboard with all it's elements and shared my 2 blogs posts as well -
one with detailed guide on twenty and other one on self hosting twenty
on our own server.
Quest:
Write a comprehensive guide on how to integrate Twenty with marketing
automation tool (n8n, Zapier). Include a concrete use case and explain
how to leverage AI to write API requests for non-developers and share
it.
Points:
1500
Hope you like the content !
### What type of PR is this? (check all applicable)
- [X] Bug Fix
## Description
This PR include fix required for issue #8058 and #6741 .
- Fixes visibility of currency symbol on hover over field
- Fixes visibility of task icon symbol on hover over field
## Related Tickets & Documents
- Closes#8058
- Closes#6741
---------
Co-authored-by: Félix Malfait <felix@twenty.com>
The recent addition of a "orWhere" condition to[ improve the search algo
quality](https://github.com/twentyhq/twenty/pull/7955) accidentally
broke the filter, being considered an independent "or" wondition while
we still want the filter to apply.
In this PR:
- Add support for manual triggers in the backend
- Add a right drawer to let users select the type of trigger they want
- Create a specific right drawer for database event triggers
- Create a right drawer for manual triggers; let the user select where
the manual trigger should be made available
- Create a default trigger as soon as the user selects the type of
trigger they want. It prevents the user to see empty selects for record
type and event type. By default, the database event trigger will be set
to "company.created". It should be visible enough for users to
understand what happens and choose another record type or event type.
https://github.com/user-attachments/assets/29a21985-1823-4890-9eb3-e4f876459c7a
Fixes: #7959
### Problem
- When searching in the dropdown, the results list would shrink based on
matching items
- This dynamic height change caused the dropdown to flip its position on
each keystroke
### Solution
- Added ```hasMinHeight``` as optional props to the
```DropdownMenuItemsContainer``` to maintain consistent height
- This prevents unwanted position recalculations and flipping while user
types
- The dropdown now stays in its initial position throughout the search
interaction
[Screencast from 2024-10-24
15-43-03.webm](https://github.com/user-attachments/assets/741317b7-fc5e-4874-8221-aa626a1a1747)
Fix#4244 and #4356
This pull request introduces the new "view groups" capability, enabling
the reordering, hiding, and showing of columns in Kanban mode. The core
enhancement includes the addition of a new entity named `ViewGroup`,
which manages column behaviors and interactions.
#### Key Changes:
1. **ViewGroup Entity**:
The newly added `ViewGroup` entity is responsible for handling the
organization and state of columns.
This includes:
- The ability to reorder columns.
- The option to hide or show specific columns based on user preferences.
#### Conclusion:
This PR adds a significant new feature that enhances the flexibility of
Kanban views through the `ViewGroup` entity.
We'll later add the view group logic to table view too.
---------
Co-authored-by: Lucas Bordeau <bordeau.lucas@gmail.com>
