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.
Best,
Daniel
STAGIL
You can also look into Insight to create those objects "separately" in insight schema and then attaching them to your jira issues via custom fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.