JIRA Custom Field value from CSV, JIRA service DESK

[Frank]

Hi Community.

this is my requirement. 

I have Custom Fields Site Licence#, Site Name, Address, Zip. I have all these values in CSV.

There are 6000 records. I would like to import all these records to corresponding custom fields. There will be huge performance impact when I import all these 6000 records to each custom field(my feeling).

Is there other way round where we can get the custom field value from external source?

Also when someone select Licence #, it should give me the details of Site Name, Site Address, Site Zip.

JIRA 7.10

Service Desk Project 3.10

[Cristian Rosas [Tecnofor]]

There are indeed ways to access data from external sources, but 6000 values will surely have an impact in performance.

Have you tought in not using a select list, but a free text field and the call the external data with a post function? Or use some code to call the external source after losing focus.

Also, it should be possible to code a call to the external source after some data has been introduced, for example, 2 characters... I remember seeing this in a customer instance once, and the impact was around 3 seconds to load the data

[Gregory Van Den Ham]

I'm curious about the use case scenario a bit.

Have you thought about it in the sense of creating a project, perhaps called site license, and having individual issues that are the site license with the custom fields in that project.

You could then link to that project in reference to the site license, when a service desk ticket comes up.

[Frank]

@Gregory Van Den Ham Our company develop some Video machines that goes to different restaurants and offices. So they would like to rise the request from service desk portal. And I didn't understand the project link you are talking about? 

[Gregory Van Den Ham]

In my case, I setup an asset management project:

It contains all the custom fields I needed, and I did an import into the asset management project from excel.

You can give that asset a life cycle via workflow.

Now, when there's problems with it, we open up jira service desk tickets and link those tickets to the asset.

What we end up with on the asset is a whole bunch of linked tickets, but that tells the story of the asset - how many times its failed, had customer calls on it, etc.

You can see in the first screenshot a linked ticket that was resolved.

[Frank]

@Gregory Van Den Ham Thanks for the replay. My project is similar to your workflow. I have Serial Number(Single Choice) which has 6000 values. Importing 6000 Values is effecting the performance.  It it taking 5 minutes to get the list of Serial Number. 

[Gregory Van Den Ham]

As a pick list?   I can see why that would load.  Mine is a custom field, but is not a single select list.