Great minds think alike

Context At the top of pipeline & list views there are filters that are displayed which do not require users to click 'Advanced filters'. The properties displayed are currently determined by the secondary properties chosen for custom objects, for standard objects these are default We have multiple pipelines & record views for different business processes Multiple teams may use the same pipeline for different processes.   The challenge we're facing today The properties displayed are not relevant to every team/user, forcing users to use advanced filters more often (extra clicks) or creating additional saved views (Which are rather unncessasary and bloats saved views/makes it harder to navigate). Deal pipelines are especially troublesome if you have multiple HS user properties. Users will often confuse the default 'Deal owner' property with the custom HS property they actually wanted. We can edit the secondary display properties in custom objects, which partially resolves some of the challenge. We can't edit the secondary display properties for standard objects however.   What we want We want to change the properties displayed here depending on the view chosen If no view is chosen, we want default properties to be displayed depending on the user's team AND/OR the pipeline the user is viewing  If the above can't be done, being able to edit which properties are secondary for standard objects would be a step in the right direction and is probably a quick win. ...read more

From the index view on any object type, we can check boxes to select multiple records and a Bulk Actions menu appears:   Please add the ability to "Bulk Associate" records to this menu.   This should honor the association settings and limits defined on the object settings. For example, if Ticket associations are not enabled, the option to associate a Ticket record won't appear.    Or if there is a finite number of maximum associated records, it would prevent the user from exceeding it via the Bulk Associate action.   It would be even better to set Association Labels in this same manner or remove associations entirely.     ...read more

Hello product team,   For HubSpot admins, one of the biggest challenges is keeping a portal organized, cleaned up and prevent overall chaos. Especially in Enterprise portals with sometimes hundreds of users, it's almost impossible to get users to follow a naming convention for email names, landing page names, workflow names. Quickly this becomes a cat and mouse game where HubSpot have to constantly chase and remind users to name their assets correctly.   Why is this currently a bad user experience for users?   Naming conventions are usually documented outside of HubSpot, in a wiki, stored as a Google Doc or something similar along the same lines. Forcing them to interrupt what they're currently doing, look up a naming convention and then come back means that they're losing time. They also have to leave HubSpot momentarily. Even then, they might misunderstand the naming convention and type in an incorrect name.   Why is this currently a bad user experience for admins?   Incorrect naming means that list or workflow filters for Recent conversion might not work. It can also mean that reports become a mess, if these reports are pulling in asset names.   If admins have to look into this on a permanent basis, in portals where there are new assets every day, this takes time away from developing the HubSpot portal and generating more value for all users.   Here's what a solution could look like   To solve this, it would be great if there were tools to enforce a naming convention. Ideally, admins would specify what constitutes a correctly named asset and similar to the forms editor, arrange fields to their liking.   Here's a quick mockup of what this could look like when creating a new page.     The user could select from dropdowns which team they belong to, the language of the assets, the asset type, include a title and date. The system would then generate a title from this that cannot be further edited.   Admins should be able to specify the options for each dropdown, separators, order and field validation (e.g. max length for a title).   (In case this is eventually introduced, please consider to make this a feature that is at least included in all Professional and Enterprise subscriptions.)   I would love to see this for all assets in HubSpot: emails, workflows, lists, campaigns, imports, properties, files etc.   Thanks in advance for reviewing! ...read more

Current State: Currently, there is conditional logic which can be applied to pipelines of tickets on the ticket creation form. This allows you to add dependent properties when creating a ticket under a certain pipeline.   Dream State: Add associations to the existing conditional logic screen. So instead of only being able to add dependent properties, also include dependent associations.   Use Case: We have a custom object for countries (we have a lot of data that needs to live under each country) but only some of our ticket pipelines require an association to a country. Currently, we can only require users to add an association to a country at the highest level of the ticket creation form which applies to all pipelines. Now we have to rely on users to remember to apply the association since we can't require it. ...read more

Our team is highly reliant on app functionality and we have created custom objects as part of our workflow.   Right now, when you search in the app, it does not search the custom object.   For example, I have an object that tracks airplanes. These airplanes are typically identified by their make, model, serial number, or registration number.    So a sales rep is on the road. They get information on the aircraft, the registration number, and put it into the search, N123HS. Currently, it will pull up any information if it was in a free text field in company, contacts, notes, etc., but it does not pull up all of the information associated with that particular aircraft in the custom object or that that object is associated with any of the standard objects.   The associated data is available if I look up a company or contact and if the aircraft is associated. But typically the company and contact is what I am trying to locate based on the aircraft data.   My prior CRM allowed for us to modify mobile views for our needs, this would be extremely beneficial for the user experience and adoption. ...read more

With the beta launch of the Track Property Changes functionality, would be good to add if we could backtrack the changes.  The new beta only allows you to track only after the event is created.  ...read more

Currently Custom Cards & Custom Timeline Activities are not available on Custom Objects limiting capabilities to extend HubSpot.   This idea is to support Custom CRM Cards and Custom Timeline Events on Custom Objects: https://developers.hubspot.com/blog/how-to-set-up-and-use-hubspot-crm-cards https://developers.hubspot.com/docs/api/crm/timeline  ...read more

It would be useful to be able to personalize the display of search results. Our Custom Objects are always in last position while for us it would be more practical that they appear in the first results :     ...read more

Can we have an Export button to Export Leads?   The Idea Category does not include Objects so used Custom Objects althought this should just be the Lead Object. ...read more