Up to 164 votes til now, but can’t see why HubSpot would need more usecases. This logic is the same in tickets and deals and we simply needs pipeline specific properties…we don’t need the same view for all pipelines, it simply does not make sense.
Again, I may share why this is urgently needed for our internal workflow for us: (Tickets)
If you see pipelines as independend processes it totally makes sence not to see the same properties each pipeline, but rather set custom specific properties each pipeline.
Usecase:
Pipeline A: Incoming Claims from Production (product damage, or shipping damage)
Pipeline B: Returns Process (We need to inform our customer that a parcel has returned and need to aglin with them and send the item out again to an ( possibly updated) address.
Pipeline C: Address-Issue (at that stage we are unable to ship the orders, since we need to get in touch with the customer)
Currently I must set one propertie with all possible propertie values of A, B & C, which makes it confusing. Plus if we had that feature done, the ticket surface or mask would reflect the actual cases and properties in a correct manner, not everything bunched together…
I rather have specific properties and values for each A, B & C and set in which pipeline they should go and hence be reflected.