Hey there, @jadjugah! Awesome question and appreciate you reaching out!

Do you mind clarifying which triggers and actions you’re using with ConnectWise and Jira?

It’s possible these fields aren’t supported in one or both apps. I’m happy to double check and add you to any existing feature requests though!

We’ll keep an eye out for your response!

My zaps goes like this: When a ConnectWise ticket status changes, an Issue is created in Jira. It pulls in all the ConnectWise fields, but I notice the Initial Description returns “no data” meanwhile the data exist in ConnectWise. 

Hi @jadjugah ,

Thank you for sending over those details! I’ve been checking this and at the moment the ‘Initial Description’ field field is not supported in the “New/ Updated Ticket” trigger. However, we have a feature request open for this, to which I’ve added your email. 

While we can’t guarantee that a timeline for it to be implemented, we’ll let you know by email if it is!

Thank you, and happy Zapping 

Hello,

We have  a forum in HubSpot that we want to create a ticket in ConnectWise mange, but the form data i cant find a way to add the filed into the Ticket in Mange as a note or the Initial Description.

Its not useful to create a ticket with no info,. 

I also would like the Initial description in ConnectWise Manage added. Is this a thing yet?? 

Hi @LinksTechnology

The initial description hasn’t been added to the New/Updated ticket yet, I’m sorry about that. 

I’ve added you as an interested user for that feature request. This lets the ConnectWise team know how many folks would like to see this addition and we’ll send you an email when we have an update.

We are in need of the “initial description” as well, please +1 for me and put me on the list for when this is available.

Would also like to see this - its very much needed.

Sorry we missed your replies here previously @MythosJames and @Techbundle! 

Happy to confirm that I’ve added both of your votes to the feature request. I’m unable to give any sort of timeline as to when you can expect this to be implemented by but we’ll be in touch via email once it is! 

+1 for me too

Thanks for reaching out here @NoelBradford.

Your vote has been added to that feature request too. We’ll drop you an email if it’s added! 

There is kind of a workaround using the API Request Beta action.

Thanks so much for letting us know @NoelBradford. Really pleased to hear you were able to set up a workaround using the API Request (Beta) action for ConnectWise Manage - great work!

For anyone else that comes across this and wants to give that API Request action a try, please check out our Set up an API request action guide for more details. 

We also need this "initial description" working

Thanks for reaching out here @Champnet. 

We can’t make any promises around when it will be added but I’ve added your vote to the feature request which will help to increase it’s priority. We’ll send you an email notification once it’s added! 

This is arguably the most important part of a ticket.  What good is this integration without it?  Why even offer it to users if it doesn’t work?  The workaround is to use a Beta feature?  0/10

Totally hear you on that, ​@tydonk! Since the ConnectWise Manage integration is maintained by their own developers, we don’t have any insight into their roadmap, but I’ve added your vote to the feature request to make sure they’re aware of the increased demand for this improvement. We’ll be in touch by email once it’s added.

I can see how the workaround of using an API Request action to get the missing details for the ticket isn’t ideal. Instead, perhaps you could set up a webhook or callback on ConnectWise’s end to send the full ticket details directly to your Zap. If you haven’t used Webhook triggers in a Zap before, our Trigger Zaps from webhooks guide is a great place to start. 

Hope that helps. Let us know if you have any questions or run into any trouble on that—happy to assist further!

Thank you for your reply to my angry rant.  I understand that ConnectWise manages their own integration.  If I could make a suggestion, tighten up developer requirements so they can’t display mappings that don’t work.  If they are a developer on Zapier’s platform they represent Zapier, so while they may develop these integrations, it still reflects poorly on Zapier to not have controls in place preventing this sort of issue.  This isn’t Kickstarter.  If it’s on the platform as an option, I expect it to work.