Creating Jira Issue should not be tied to the HubSpot Ticket object. Automations should be able to be kicked off to create Issues in Jira from any object and the Jira create/associate card should be visible from more objects than Company's.
For example - we want to be able to create a Jira Issue for our implementation team with details from a Closed Won deal via automation. Without the Ticket object this is not possible so you cannot automate it.
Another example - if an AE needs resources prior to the closing of a deal they would be able to create a Jira Issue from the Deal thats sends to the technical team to prioritize and assign support without forcing members of the team to move to chat channels.
I have the exact same problem! Jira issues should not be tied to the ticket object only, but it should be possible to associate it to a Deal, without a ticket "in between". To avoid this polluting my Support metrics, I've created a workflow that closes these tickets automatically, but an improvement here is much needed!
This is by far the most popular use case when using HubSpot and Jira together. You can see the demand by checking the template libraries of no-code automation tools. We currently have one customer that also needs a trigger in Jira when a deal is tranfered to "close won" and its not really satisfying when you have to suggest a no-code automation tool.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
