I have been battling with this for months, so hope to get some input from some experts here!

Context:
We offer different laptops to new and existing employees based on their department and role. 
So if they’re an Engineer, they choose Mac or PC options from a list of specs suited to Engineers.
If they’re in Finance, it’s a basic Macbook Air or PC. And so forth. 

Our current setup:
1. Employees log a request ticket via JIRA Service Management which goes to approvals.
2. Once approved, the persons responsible for purchasing need to liaise with the requester to find out what screen size, etc

Issues with current setup:
1. Staff have to remember the URL to the specific portal that has the ticket type they need to select
2. The ticket is only capturing very basic details (name, manager, laptop preference (Apple vs PC).
3. Adding complex conditional logic in JIRA (to show which laptops they can choose from) is hard in JIRA (so I was told by the person who inherited the responsibility of the ticket setup)
4. The approvers don’t get enough information from this basic ticket to make an informed decision of whether they can approve the request or not. They need to be able to see what the employee currently has, does it meet our current specs on offer for that department, and does what they have chosen match up to current specs on offer, and so on
5. Once the ticket is approved, we then manually have to pass information to the persons responsible for purchasing the device. Currently they are still having to go to the requester, ask them which specific laptop they want (screen size, etc.). So there is still alot of back and forth which is unnecessary (and should be solvable with Zapier!)

This is what I am trying to achieve:
1. I have set up Workflows in Slack for employees to commence the request process - this solves the problem of having to remember the URL to go to when they need to make a new request. The workflow has a link to run the Laptop Request process in Process St. 
2. We already use Process St for Employee onboarding tasks. I have already set up a workflow to capture replacement laptop requests from existing employees. This workflow captures data like their personal details, their current device, why do they need a new laptop, then based on conditional logic it shows them what devices are available to them to choose from. They choose their specific device. 
3. When they have completed the workflow in Process St, I want to trigger a new JIRA Service Management ticket to auto-create. This should then push the relevant details from the workflow in Process St, to the ticket details in JIRA.
4. Only at this point the new ticket is created. 
5. The workflow in the ticket then pushes to the approvers (their Manager and the CFO) - they now can see all the relevant details in the ticket at a glance, and can quickly approve the request. 
6. Once the ticket hits the next step in the workflow (Waiting for Support) it should then trigger a secondary workflow in Process St which feeds the laptop selection to the person responsible for making the purchase. They have all the details already. There will then also be subsequent steps for the employee to confirm receipt of their device, register it for security, etc - but this is all captured and set up in Process St already. 

THE ISSUES:
1. Process St has JIRA integrations but it does not support Service Management tickets, only JIRA software. So I can’t trigger a new ticket from the Process St end. 
2. Using Zapier to set up the JIRA ticket doesn’t work either (trigger: workflow completed in Process St). It is a known Atlassian issue that there are fields in JIRA that are not populated within the Create Request action in JIRA. There is a public feature request on this with Atlassian but I was told by a colleague that worked for Atlassian, that the chances of this feature ever going into production are slim to none!
3. I cannot set up the ticket type in JIRA itself to show the laptop options available to choose from based on complex conditional logic (that we have in Process St).

WHAT I AM LOOKING FOR FROM THE COMMUNITY:
1. Any clever workarounds you can think of?
2. Bright ideas on how to solve this problem? 
3. Should I change the ticket type setup in JIRA?

Please help! It’s driving me nuts!