I'm preparing a csv file with the source information from unfuddle. Initially, the work items are all bugs. I'm hitting some issues in the import and hope that you can help. The challenges are that:
2014-09-24 14:39:51,419 ERROR - Issue can't be created due to the error/s [ User 'xxx' cannot be assigned issues. ]
If there are some guidelines as to how to prepare/sequence the import, that would be great!
The most useful documentation will be shown at the bottom of the failed import screen, so be sure to read the guidance you're given there. Unfortunately, the CSV import documentation isn't as complete as it probably should be. We do a lot of migrations for our clients, and they can be quite a challenge.
Regarding your questions, here are some things to look into:
I hope that helps.
Thanks for the pointers. Your guidance on the assignee field worked.
The mappings I'm receiving don't seem to have any accounting for an "Issue Created" field. I'm trying to pull these into a JIRA Agile/Kanban project. Is it possible that I need to modify something in the project to allow for that field to be imported?
I didn't have a CSV handy to do a mock import, so I got the exact field mapping name wrong. It's called "Date Created." It's not a field in the sense where it would show up in Custom Fields. It's a system field that is set when an issue is opened. It is something you can map in the CSV import wizard, though, as long as you have a column with the create dates in it.
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs