Propose new Mautic features
#MauticRoadmap Building Mautic together!
Make Field Group Bundle part of Mautic Core
Has your proposal been discussed on the Mautic Forums already?
Yes, multiple times. Here is a thread with one of the most recent replies: https://forum.mautic.org/t/merge-custom-fields-group-bundle-to-mautic-core/28960/4
Is your feature request related to a problem? Please describe.
Some Mautic users, would like to have additional field groups as opoose to just the default ones.
Describe the solution you'd like
At the moment you can add additional field groups by doing some coding. I would like to eliminate the coding part, I want user to be able to add additional field groups into Mautic without a need for a developer.
Describe alternatives or workarounds you've considered
An alternative to this bundle is that you extend the form type, but you need to hire a developer to handle that for you.
Additional context
As an author of the plugin, I can say that it felt like plugin really helped out some people and provided a much needed feature.
I would also like to point out that the plugin works and most of the work has already be done, so I can start with the merging to core pretty quickly.
I would kindly ask the team, in the event that this actually passes the proposal stage, that someone answers to my questions expressed in the forum post here: < https://forum.mautic.org/t/merge-custom-fields-group-bundle-to-mautic-core/28960/4?u=mzagmajster >.
Thank you.
Does this issue could impact on users private data?
No, I do not think so.
Funded by
Project funded by Adra Cloud, coded and maintained by Matic Zagmajster
Estimated cost
It'd be great to try to get this into the 5.2 release, if it's not a BC Break.
Project funded by Adra Cloud, coded and maintained by Matic Zagmajster.
This proposal has been accepted because:
Thanks for all the discussion and debate, this feature will be great to bring into Mautic.
Proposal appearing in these projects:
List of Endorsements
Report inappropriate content
Is this content inappropriate?
Comment details
You are seeing a single comment
View all comments
My suggestion;
Put everything into LeadBundle (db entity, api endpoints, standard controllers for gui).
Dispatch event LeadEvents::FIELD_GROUP_LIST_ON_GENERATE before displaying (in controller most likely) for the following templates:
https://gitlab.com/adra-network/mautic-field-groups-plugin/-/blob/main/Views/Field/list.html.php?ref_type=heads
https://gitlab.com/adra-network/mautic-field-groups-plugin/-/tree/main/Views/Lead?ref_type=heads
Create FieldGroupEvent, with the following implementation:
getGroups()
setGroups()
Change the templates so groups are used without hardcoding any translation strings.
Remove the publish/unpbulish feature from GUI
Allow to transfer fields from one group to another
Only allow to delete a group if no fields are in the group (also display number of fields in the group)
Update Tests
Elemnets we do not need anymore:
We do not need this: https://gitlab.com/adra-network/mautic-field-groups-plugin/-/blob/main/Form/Type/FieldGroupExtensionType.php?ref_type=heads (since we will adjust the type in the core).
We do not need this anympre: https://gitlab.com/adra-network/mautic-field-groups-plugin/-/tree/dev_mautic5/Translation?ref_type=heads (since field groups will have nothing to do with the translations when we are done)
Let me know if you are OK with this approach or is there something you would like to change / add. Thank you.
Loading comments ...