As your friendly Jira Administrator. :) CSV import is intended to be a migration tool and not something you use on a daily basis, so that's why it's access is limited to the administrators.
You could write a script and pump the data in via the REST API, though. All you need is Browse Project and Create Issue permissions (and some scripting skilz) if you go this route.
Not everyone can code - so yes the original poster above, and myself, use CSV import frequently to manage multiple teams.
I have been unable to permission users to import into projects - they have to be system admins. if that is out of date please point to a how to grant non system admins permission to import into a project.
At this time i want to figure out how to ask for a project level import permission to be permitted as it's very frustrating how limited import is.
@Nicole Schwartz, you are correct. You must be a system-admin in order to use the CSV import feature. It's intended to be a migration tool, and not something that you use daily. This is why it requires administrative permissions.
I'm not sure of your exact process, but we occasionally see teams that hash out their backlogs in spreadsheets and want to import those issues in to Jira easily, so they propose using the CSV input method. If that is more-or-less what you're doing, I suggest moving the backlog creation in to Confluence. It has an easy ability to open Jira issues from within a Confluence page. They don't call it out specifically, but modern versions of Confluence can open multiple issues with 1 click if the issues are in a table. Essentially what you do is create a table in Confluence and add your backlog in the table, then when you highlight one cell in the table, it will see that the data comes from a table and ask if you want to open multiple issues. You then select the Project and Issue Type. It's pretty simplistic, so you may need to add additional detail to the issues once they are in Jira, but it's another alternative that doesn't require admin access.
@dave Theodore [Coyote Creek Consulting] Thanks however the click to create issue allows me to only set a few fields
When i have a new epic, i know there is going to be at least 50 tasks and 10 stories and i roughly know what they are. I have a CSV template to start with, tweak, then import. BAM done. It sets many columns - planned quarter, assigned team, estimate hours per task, story points, this is all done in one blow - populates our epic and allows us to review the backlog and put things into sprints.
Confluence does not allow for that level of power multi entry, even with the multi-add option you described.
There is little reason that this should not be it's own permission I can assign to scrum masters who I have reviewed how to do imports with.
And excel is already something work has purchased, where that add-on is yet another thing we would have to pay for. It's frustrating that a feature that is there, is something i can't control, and the "fix" is to pay money.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot