You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
My users are using CSV to collect data and then importing via the user CSV import. This works as long as you are importing to the first issue type but I don't believe you can map IssueType unless you are admin, is this correct? Any easy work around on this?
Not really, because only Jira Admins would be able to create new Issue Types.
Apologies for not being clear. I am not creating new issue types, I just want to import in a different, already defined issue type. In my example, my first issue type is "User Requirement" and the second is "Functional Specification". The user import looks like it will only import to the first issue type "User Requirement".
When I create an issue on the GUI, I have to define the project and issue type while it appears that when I "import issues from a CSV" I only define the project. Is this a major oversight or am I missing something obvious?
While it is true that holding administrator permissions more options are available for CSV import an user can import defining Issue Type without any problems.
I believe you are referring to this general information:
If not specified in your CSV file, imported issues will be given the default (i.e. first) Issue Type, as specified in your Jira instance.
But looking at the CSV file you have several options - one of them is to assign an Issue Type:
IssueType, Summary, Project Name, Project Key
bug, "First issue", Sample, SAMP
Please also review - the documentation explains it a lot better than I could:
My CSV contains IssueType and this works successfully when importing via the admin approach but using the standard user method it does not. When you map IssueType only the fields visible on the create screen are selectable which does not include IssueType. In the admin mode the issueType is available to select. The documentation link attached does not distinguish between the modes.
I am very willing to believe I am doing something wrong but to me it does look like a major drawback with this approach.
Viewing the example data I presented you in the answer above I went to a Jira Server instance where I am definitely not admin and got a positive result. (Jira version 8.3.4)
Note: by purpose I did not select the standard value "bug" but a more rare one.
So the Issue Type is to be mapped (on the following page the Issue Type even could be selected so I went for an even more special one) - and the import worked out. Do you see the same information when trying to import or how does it present the window to you (as user, not admin)?