I want to move a single project from a Jira 5.0 instance to a new Jira 8.0 instance being already used for other projects - so the process must not bring in configurations, workflows, etc. nor should alter existing projects.
I'm only interested in importing issues and related data:
title, description, etc (obviously)
attachments (images, files, whatever)
issue links
issue type (with mapping to new types in case they don't match)
... (other properties that I'm forgetting right now)
I've just started searching for the topic and already found several options - and it's not clear if they're all available to be, mosly due to the starting Jira version, they are:
Export to CSV and import to CSV
Export to XML
Import from JSON (though I've yet to find a JSON export)
Rest API
Import project from backup
... and surely others
Of course I'd like the most complete yet less error-prone method, though if resorting to the REST API will be the only way to be sure to import all I want, I'm ready to write a script / program.
So, what should I choose?
P.S.: I'm not sure if this fits this community, is there a more proper one?
The easiest way is to get csv export, get all attachments (jira_home/data/attachments). Then copy attachments to a new instance to jira_home/import. You'll need to edit export file to match names and paths of your attachments in order to import them successfully.
And last step is import csv to your Jira 8 instance.
I suggest trying this on dev/stage environment first because there are many small details that can affect import.
Some useful data is here:
https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html
Related
Currently I have a CSV with two columns:
is test of
is tested by
When I import the issues I map them by Links and Sub-Tasks/Issue Id.
However, after completing import I do not see the links on any of the tickets.
How do I use a CSV for import and link the new issues to existing issues?
Note: https://confluence.atlassian.com/display/JIRAKB/How+to+Import+Issue+Links+from+a+CSV+File describes how to link new issues to new issues, but my goal is to link new issues to existing issues on import.
Not sure why this failed originally. This time I simply made a test CSV with two columns (summary, is tested by). is tested by then had an existing issue id in it. Map the is tested by column to a link.
Import.
Done.
The neo4j example data does not work in the most recent version 2.1.2 of neo4j as documented here and here. They are built for 1.9 and apparently can only be upgraded to 2.0, not 2.1. Is there a way to extract the raw data as a csv or cypher file (with a bunch of CREATE statements) from either the tarballs (which contain a graph.db, which I do not understand) or the associated github repositories (which I also do not understand)?
It's up to us to update the datasets, thanks for pointing it out, I think we'll also put them into versioned subdirectories, so it is easier to see which version they are in.
In general for small enough datasets, you can use the neo4j-shell and the "dump" command to generate cypher statements.
Also in the neo4j browser you can actually download the query results as CSV.
I also wrote a set of helper tools for the neo4j shell that allows you to export and import data as csv, graphml and other formats.
I would like to give my users the ability of export and import their posts on my server, including images, comments and whatever linked data to the object.
Basically I would like them to be able to click somewhere and receive a zip file, if they open it they will see several xml, or json, or yaml files and the image files that were part of their posts.
They can then upload the files and have back their posts in the way they were when they exported.
I couldn't find any tutorial, or gem to help me in this, would you be able to recommend me the design to approach this issue?
thanks,
In the past I did it this way for exports:
Create a new temporary directory
Serialize everything you want exported to your format of choice and write it into a file in that directory
make sure the images are clearly identifiable, e.g. by serializing their file names instead of arcane IDs
copy the image files in the temporary directory
zip the whole dir (can be done via system commands)
optionally, but it's a good idea: move the whole shebang into a background job and notify the user once their file is ready for download.
I'm not sure if import is feasible this way, or even a good idea, but you can try.
One neat trick to specify which fields/attributes are exported is to overwrite Record#attribute_names.
Say you want to export only title, body and creation date of a Post object that usually also has updated_at, user_id, etc.
# in the export script you'd write
class Post
def attribute_names
['title', 'body', 'created_at']
end
end
Post.export_for(#user).all.to_yaml
It's important to only do this in the export script, because you screw with record introspection here. Usually, though, the export methods (to_yaml, to_xml, etc) rely on this mechanism to determine what to export, so doing this locally/temporarily works great.
I have recently been assigned the project of reviving our old magento site, which is for a bookstore, version 1.4.1.1. The first order of business that I need to do is to update the inventory on the site, which has about 95,000 items. What is the best way to do this? My inventory is all in a mysql database currently.
Secondly, I need to upload pictures for all of the entries, is there a way/ place that I can specify a base url for the picture, and then just add the specific location (ie bookpic.isbn.gif where the isbn will change based on the isbn of the book)?
I saw a previous post from over a year ago that listed good reference sites, where can I go for updated information?
Have a look on cutesave for an easy implementation and import for simple-products:
https://github.com/magento-hackathon/cutesave
https://github.com/magento-hackathon/cutesave/wiki/Cutesave-Tests
Good luck
Another solution I've used is a dataflow profile (Admin->System->Import/Export) to import products from a flat file. I exported the products from another database to a flat file, then used dataflow to import all products.
I referenced an article that talked about modifying the profile to add an extra step to the import process where it downloads the image from a supplied URL in the flat file and saves it to the media/import directory before it attempts to check the media/import directory to import an image for the product.
I was browsing around and found this blog post:
http://erikej.blogspot.com/2010/04/version-3-of-exportsqlce-now-available.html
(It is for a great add in if you user SQL Server CE.)
On that post I saw an screen shot of SSMS with images in the results.
How is this done? I have images in my database (PNG files that are serialized via memory stream), but I just see numbers when I select the image column.
If you are asking how this is done, I'm not sure how it is implemented exactly. I know that you can create ssms plugins in visual studio, and I'm sure that there is a way to take a filestream object and decode it.
If you are looking for a way for you to do this besides the plugin you mentioned, there is a great freeware plugin I use. You can find a plugin ssmsboost at http://www.ssmsboost.com. This plugin has a community version and a pro version. The only difference between the two is that the community version needs to be renewed every 120 days. This plugin has a lot of nice features, but the one you're asking for is
SSMS Results Grid Visualizers:
Feature allows to export & view files or some big amounts of text or XML data from tables (like files from document storage of sharepoint services). Required data should be simply output to ResultsGrid. By right-clicking the cell with required value and selecting "Visualize As->.." you can tell to save data to file with predefined name and open it with custom or default application. No matter than SSMS truncates long data from VARBINARY/VARCHAR fields when outputing them to ResultsGrid: SSMSBoost works with internal storage of SSMS and extracts complete cell value. Below you can see how a picture from [LargePhoto] field of [Production].[ProductPhoto] table from [AdventureWorks] database is being visualized:
I'd like to recommend the MiniSQLQuery browser that is free and opensource to achieve this.
http://minisqlquery.codeplex.com/