Hi @David Perry
If I understand correctly, your system currently allows you to create a task in Salesforce that in turn creates a support ticket in Jira.
If your company is open to trying a different integration solution, you could try setting up a very similar connection with Unito that doesn't involve an iframe pop up at all.
You can find out more here.
To get set up with that workflow, here's what you need to do:
1) Set your Atlassian email contact visibility to anyone.
2) Add the Unito app for Jira.
3) Set up an application link in your Atlassian account.
4) Connect your Jira and Salesforce accounts to Unito through a "flow". It's a 4-step process (entirely cloud-based, no coding required) that allows Unito to pull specific task data from Salesforce and Jira and sync it to the other. You need permission to create tasks in both tools in order to do this, so make sure you're an admin or equivalent.
5) Set a flow direction to create Jira tickets from Salesforce (you can also tell Unito to create Salesforce tasks from Jira tickets/tasks if you want).
6) Set rules for when/how tickets are created. Again, it's all cloud-based, so you point-and-click with drop-down menus. In this case, I'd apply a label/tag to your Salesforce tasks you want turned into tickets. Then pick that label from a drop-down menu in Unito.
7) Link fields between Jira and Salesforce. So this step is where you'd filter out the fields you don't want to see in both tools. You create pairs of fields between Jira and Salesforce, basically establishing the relationship between them so Unito knows what to sync with what (e.g., title to title, description to description, etc.). You mentioned wanting to exclude some fields, so I would just not include them in the table of field mappings you see in Unito. I don't know exactly which fields you want to exclude, but I'd just build the table without them.
8) Launch the flow and see how it goes. Every flow starts in a test mode so you can create a new task/issue to see if it does what you want it to before applying the workflow to all your historical data/tasks/tickets. If so, you just remove the creation date filter from the rules and you're all set.
It may seem like a lot of steps, but it's much easier and less complicated than writing script, getting a dev to build code for you, or anything like that. The platform is SOC 2 Type II compliant, it's an Atlassian partner and your data is fully encrypted end-to-end.
I hope it works for you! Feel free to reach out if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.