How to CSV import security level in jira?

[Rahul Aich [Nagra]]

Hi All

I am trying to import isssues from another issue tracker using csv import feature on jira.

On my old issue tracker we had issue security, now i am not sure how to import the issue security level on jira.

I am able to export the security level (from my other issue tracker) in an csv. Now I am not sure of the procedure of importing the security level on jira.

Can anyone help pls?

Rahul

[Ruchi Tandon · Accepted solution]

Hi Rahul,

It seems that it is not possible to import security level using csv import due to the bug : https://ecosystem.atlassian.net/browse/JIM-923.

In this case, you have 2 options to set Security level for your issues :

• set security level after you imported issues using bulk operation
• obtain the JIRA source code from http://my.atlassian.comwith JIRA source code and then modify the JIRA importer source code.

[Rahul Aich [Nagra]]

Thanks Ruchi...that confirms my analysis.

[Carol Jones]

I'm unable to view https://ecosystem.atlassian.net/browse/JIM-923, can it be opened for others to read?

[Carolina SILVA]

hello, I do not have acces to https://ecosystem.atlassian.net/browse/JIM-923 either 

[Omid H.]

+1

[Mridul Kumar]

Has there been any solution for this yet?? We too are facing this issue as we have to create bulk issues and since we cannot map the Security Level to some other value it is taking it as None which means all our clients can watch every other client tickets which is a big security concern. 

For now we have to manually set the security level from None to another value but it's a pain doing it for large number of tickets.

A long term solution for this would be really helpful.

cc @Ruchi Tandon

[glennrees]

This is still a problem. My users cannot import issues via csv as Issue Security cannot be set by them. I have to do this for them as an admin and then bulk update the issue security. Kind of a pain. JIRA 7.8.0.

[Rahul Aich [Nagra]]

@Nic Brough: Do you have any suggestions on this please? I have received no response on this so far.

[Rahul Aich [Nagra]]

HI Luther

Yes, i have

1. I have issue security scheme, added the security levels that are present in my old issue tracker

2. associated the issue security to the project

3. On creating an issue on the project I see the field secuity level with the levels as I had set.

The problem is while performing the csv import, the step-2 does not display security level as one of the fields avalaible for mapping on jira.

[Luther Hargrove]

Do you have security level setup with values and showing on the create issue screen?

[Rahul Aich [Nagra]]

Hi Luther

Are you sure? On the CSV import , screen 2, we do not get to select security level as a field for mapping. It is a limitation of tool henc my query

[Luther Hargrove]

You have to have issue security enabled on the JIRA project and have the fields showing on the screens so the field can be populated. You have to have values in JIRA that you can map to from the old issue tracker. If that field and it's corrisponding values are in JIRA and available to set from a create issue screen, then you should be able to import it.