Ideas / Advice Needed for a Jira Service Desk Issue Type

[Jeremiah Fischer]

I have a process I'm looking to move into the JSD Cloud. The process is currently carried out manually and has a plethora of fields. I'm running into the limitation of only being allowed 19 fields. Does anyone have any idea how to get by this limit or how to arrange my work flow differently?

The first set of fields are basic information about the user in question (name, number, manager, etc.) the remaining fields are verification questions to ensure the user has done "x".

Any advice is greatly appreciated!

[Earl McCutcheon · Accepted solution]

Hi Jeremiah,

Where are you hitting the limitation in the fields in service desk?  Are you talking about the Visible field mappings on the request types as described in this article

If this is the case you can get more fields options avaliable by adding fields to the create screen for this this issue type.  But do be aware that some field types are unsupported and will be hidden or require a default value.

Regards,
Earl