I want to create several similar Jira tasks in Excel, tweak them slightly in Excel, and then import them to create different Jira tickets which I can modify further directly in Jira.
I already have several existing Projects in my Jira instance. I want to import these Excel tickets into one of those specific projects.
There are warnings in the documentation that importing from CSV will wipe out all existing data in the project. The existing Jira projects are actively used and I can't afford to have all that wiped out. I just want to enable ticket-writers a quicker way of creating tickets.
Is the documentation overly-cautious and/or incorrect?
Would creating a dummy project and importing these CSV records into that file and then moving them to the target project be a way to avoid this problem? I'm afraid even doing this will wipe out data and settings in projects across my Jira instance.
Take a look at this document, it explains it step by step :
Importing issue will not change any configuration settings, so you don't have to worry about that.
If you are worried about overwritting data you can first create a demo project with 1 or 2 issues in it and import your csv to this project first, after the import you can check if your original issues still exist. You can then just delete the project after a succesful test and import the data into your correct project.
I am looking at this doc about importing from CSV,https://confluence.atlassian.com/display/JIRA/Importing+Data+from+CSV and I do not see anything about wiping out data. If you are unsure use the Altlassian SDK to setup a quick JIRA instance, create a few test project and then run the CSV import. If anything goes wrong there are no worries as it was just a test enviroment.
In this document (https://confluence.atlassian.com/display/AOD/Importing+Issues) it makes the statement "This import procedure overwrites all the existing data and configuration in JIRA OnDemand and cross-application settings." but I guess that's specific to "Importing issues from JIRA and other third-party issue trackers"
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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