Customize Ticket Properties based on Pipeline

We work with several different pipelines of HubSpot service tickets.  We would like to set the default for displayed ticket properties based on the pipeline we're working with.  For instance, we want to see our custom "Serial Number" field in our RMA pipeline, but we don't need to see that field on the ticket for our "Enhancement Request" pipeline.

HubSpot updates
15 Replies
Community Superstar

_hubspot-button-accept-as-solution-gif-v00.gif

Does this post help you? If so, then help others by accepting it as a solution.

 

 Excellent suggestions. You may wish to add them to a new or existing thread in HubSpot Ideas.

 

You'll typically get much more traction from the HubSpot Community AND the Ideas Forum is where HubSpot Product Teams monitor suggestions for popularity -- i.e., VOTES! Smiley Happy

 

Hope that helps.

 


Your Remote HubSpot Partner

www.MFrankJohnson.com

 

Please include @MFrankJohnson in your message if you'd like me to reply.

JonnyT
Occasional Contributor

We work with several different pipelines of the HubSpot service tickets.  We would like to set the default for displayed ticket properties based on the pipeline we're working with.  For instance, we want to see our custom "Serial Number" field on a ticket in our RMA pipeline, but we don't need to see that field on a ticket in our "Enhancement Request" pipeline

 

Screen Shot 2018-06-27 at 1.30.19 PM.png

chung
Regular Visitor

I have the same problem. It is quite surprising that hubspot provides a way to separate the tickets with pipeline, but they don't provide a way to distinguish the tickets.

 

What's the point to put identical tickets into different pipelines?

 

I am going to have 5 pipelines and I can foresee the tickets will have at least 10 irrevelant properties when I finish adding the properties to the same pool.

 

I feel that the pipeline feature is just halfly done only.

chung
Regular Visitor

I have the same problem. It is quite surprising that hubspot provides a way to separate the tickets with pipeline, but they don't provide a way to distinguish the tickets.

 

What's the point to put identical tickets into different pipelines?

 

I am going to have 5 pipelines and I can foresee the tickets will have at least 10 irrevelant properties when I finish adding the properties to the same pool.

 

I feel that the pipeline feature is just halfly done only.

propeller_joni
New Contributor

+1

 

We have several very different pipelines, and each have different properties that are relevant.

drakedanner
Regular Contributor

We also need this. We love ticketing functionality but need different default properties for different pipelines. The pipelines serve very different purposes.

drakedanner
Regular Contributor

Adding my voice here -- the functionality of the ticketing tool is very helpful for a variety of processes where we need oversight around getting a task completed. But we've built out the properties to aide in very specific processes. Now we want to utilize the tool for other processes but the default properties are not relevant for these new processes. 

 

I would like to be able to set the default visible ticket properties for my team for each pipeline.

vlouvet
New Member

 This feature is highly sought by most enterprise customers arriving from Zendesk.

jyarish
New Contributor

JonnyT - spot on!  

No need to have more than what you need for each pipeline.  Unused fields add to confusion and inconsistency.  This is a significant loss when moving from a dedicated issue tracking platform to HubSpot.  

Dramaboy
Occasional Contributor

Any advancement on this topic?  This is an issue for our business as well.