We have various pipelines, for various sales cycles and sometimes various types of contacts or companies.
The Deal's information we need to access depend on the pipeline the deal is in. Since the "default deal properties" is made to display the "most important" information of a deal, we need this group of "most important" information to be pipeline specific.
To propose to create multiple "default deal properties", each one having a name. Then, admin should be able to decide to which pipeline to apply this "default deal properties". A "default deal properties" may be applied to one or more pipelines. It's ok to have a limit on the possible numbers of possible "default deal properties" if needed. 10 or 20 maximum would already be amazing.
Note: I've written the above with the understanding that "default deal properties" are controlling both the "about" section on the deal and the properties available when creating a new deal on the card that's opening on the right of the screen.
Weitere Ideen mit folgender Beschriftung anzeigen:
This original idea contained 2 great feature improvements that are different segments of work for our teams and cannot be completed in tandem. Since we have delivered on one of the ideas, our community team has advised that we keep this idea marked as "delivered".
However, since the other half of the suggestion is yet to be implemented (the ability to use different properties upon deal/ticket creation), I created another idea to track development. I've also set the idea to "In planning" as we are actively determining the best way to solve this problem and it is something we do plan to implement.
Thank you for your continued feedback, I'm also looking forward to marking that idea delivered as well!
When combing through the thread, I did notice this to be about 30% of the case that was mentioned. Unfortunately, this is not part of the update I posted about above but it is firmly on our radar.
We are beginning to kick off work on that front (creating deals) but I felt as if the majority of the asks here were around the data that displays on Deals. We're well aware of the case for conditional required properties based on a pipeline an object is created in and will update this thread (or another, if it pops up) once we have that in a beta!
Thanks as always for your continued feedback on our product
Thank you for your continued feedback and input on the Community. I'm excited to update this post to "delivered", as of today we have introduced the ability to display conditional data on records into beta. Here is a knowledge doc that explains the capability.
In short, Professional users can now add customizable sections to their records; Enterprise users can customize what displays on records depending on the team a user is on or a property on the object (ex: pipeline). This update also comes jam-packed with property updates, such as the ability to delete or regroup HubSpot Default Properties.
We'll have a more detailed product blog post coming soon, but I wanted to personally let all of you on the community know first!
If you're interested in using this functionality - navigate to "properties" within settings. If you are a Super Admin you will see a toggle in the bottom left hand corner that will allow you to unlock the new experience. We hope to make continued improvements to this experience before rolling it out more broadly as the defacto experience.
As always, thank you for your continued feedback. Here on HubSpot Product we're always eager to improve your experience to help your business grow better!
We really appreciate the continued feedback on this post. Allowing pipeline specific deal properties is certainly something we hope to look in to. However, at this stage the work has not been planned or scheduled. Please continue to provide examples and use-cases for this feature - it will help us build a better solution when the time comes. We'll update this post when we have further clarity on when we plan to build this functionality.
Hi HubSpot community - thank you all for providing your feedback on this issue. I'm a member of our Product team and I wanted to let you all know that this is something we are actively thinking about and hope to deliver soon! Please continue to provide examples and use-cases on this issue, I will provide an update once this functionality is closer to beta.
Sie müssen ein registrierter Benutzer sein, um hier einen Kommentar hinzuzufügen. Wenn Sie sich bereits registriert haben, melden Sie sich bitte an. Wenn Sie sich noch nicht registriert haben, führen Sie bitte eine Registrierung durch und melden Sie sich an.