You should convert each part of that form into a Jira field.
It looks like some of those contain variable length tables - if you want to do those, you'll need to teach your Jira people to use tables in text fields, or use something like the Table Grid app to provide them.
That's a basic Jira functionality, capturing data in forms ;)
What exactly are you missing when using issues and custom fields for this?
As mentioned by Nic, you can use custom fields for single values like CPU, Memory, etc. and for fields like Disks and Network Interfaces you could use table fields - e.g. with the Tables add-on - which are also custom fields but in the form of a table, which you can also include in your JQL search.
This looks like a server to me, so you can create a new issue type called "server" with all those fields and that's how you made an asset out of it that you can manage in Jira with a workflow, fields, links, etc. Now you can link it to your incidents, service requests and so on. If you would like to have special custom fields on your linked issues where you can only select a server or specific types of assets for e.g. maintenance requests, you can create issue picker fields, e.g. by using Assets - Advanced Links.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event