SCREW JIRA CSV IMPORTER AND GET MORE JIM JSON Importer
WHY• CSV import is the most popular import source• CSV is the easiest for many users and experts: its easy to create a text ﬁle from any script, language or SQL query• CSV is bad for representing complex, hierarchical data and 1:N relationships (comments, worklogs, subtasks, timestamps)• CSV uses various ugly hacks to get more from ﬂat ﬁle, like author;date;comment body• CSV importers does not support issue change history
JSON FORMAT• Human readable (similarly to CSV)• Less verbose than XML• Easily represent hierarchical data and 1:N relationships• Easy to generate, easy to author manually (Sample Data)• Much more feature complete than CSV• Support dynamic interpolation of variables just in time (Velocity) via JIM API.• You cannot save it from a spreadsheet editor, but you can save it from JIRA :)
WHEN I WOULD USE IT• Importing customer data• Preparing demonstrations for customers• Preparing training classes• Preparing test data for your plugins/products
CAN I USE IT?HOW ARE YOU SERIOUS ABOUT IT• Well its formally BETA, but ...• GreenHopper has just started using it for its new users onboarding (as of 6.0.3 - released 4 days ago)• JIRA is to use it too very soon
I WANT TO KNOW MORE• Export issues to JSON from your own JIRA (enable modules ﬁrst!) and see how it looks like• JIM JSON documentation on CAC is minimalistic• JIM source code and test ﬁles (src/test/resources/sample/)• GreenHopper sample data post for Experts
THE FUTURE• Support for attachments from various sources (now only via API)• Maybe support for more meta-data (e.g. dashboards, saved searches, project conﬁguration)• Your requirements & ideas!