I have been searching the Tool(freeware) for a clean solution on how to migrate tasks from JIRA to TFS2012.
Already i try to setup tfs-jira-synchronizer setup
I've been trying to set this up on a sandbox server however when I ran the installer I didn't get the acl application file in my virtual directory.
The installer completed without errors.
I recently had to migrate from Jira to TFS.
I ended up writing my own utility to do so. I felt this was a good candidate for 'open-sourcing' so have published it on GitHub here:
https://github.com/KilskyreMan/JiraToTfs/releases
(tested against TFS Server 2012, 2013 and 2015)
Utility handles all main and custom templates, links and attachments.
Documentation can be found here: https://github.com/KilskyreMan/JiraToTfs/wiki
Hopefully this can be of use to other people in this situation.
Cheers - Ian.
Try the integration platform.
http://tfsintegration.codeplex.com/
It's buggy, hard to work with, and usually really annoying but it is your best bet.
There is also this: https://marketplace.atlassian.com/plugins/com.spartez.jira.plugins.bork.tfs4jira
for synchronizing the two systems
If you want a one-time migration of data, I don't know of a free tool for that. I'd probably start with looking at the data formats that TFS will accept, then write a tool that parses an XML backup from JIRA to create a file in a suitable format for import. You could even use the JIRA REST API to get the data but that might be slower depending on how much data you want to export from JIRA
Disclosure: at ServiceRocket we do many data migrations into JIRA each year.
Related
I am transferring a jira issue to TFS WIT in my company. My team used TFS2012, they use JIRA. So I want to migrate the JIRA issues into TFS2012 WIT.
I want to preserve all the basic fields, attachments and comment history & work logging.
Any suggestions regarding tools or processes for this?
I looked into dumping the issues into an Excel spreadsheet, but that doesn't include attachments or comments.
Integration Platform
Good luck, the migration isn't usually a lot of fun.
using comment-plugins we can export comment on excel....
here we can find the comment plugins
https://confluence.atlassian.com/display/JIRA/How+to+add+comments+to+Excel+export
(we could map this to History field in TFS once we export it to Excel)
nearly 3week i worked on this task
finaly i got it
For this task we simply add USETFS plugin in jira that carry everything i mean comment tfsid and attachment everything its come under USETFS plugin in jira.
Is there any way of exporting Test Cases and Shared Steps from one project to another in TFS 2012 using database queries?
I have tried TFS Integration tool, but it did not work as I expected, so I was wondering if there is any way of doing this by connecting to SQL Server and exporting all items directly from and to the databases.
A few days ago I needed an Excel testcase export for a newer version of TFS (TFS 2013). Turns out that there is still no export to Excel function built-in to TFS (in contrast to E-Mail and Printing) and the tools became incompatible over time.
But I found this Revival-Tool that seems to work:
https://github.com/jorupp/ExportTestCases
Just wanted to point that out even if it may not be directly related to this topic with TFS2012.
You shouldn't work directly in the database, because it is not supported by Microsoft and you could harm it a lot.
I used the TFS Integration Platform tools a lot for migrating TFS2010 projects, but never used it for TFS2012. My experience with that were good and it shouldn't be a problem to migrate all Test Cases and Shared Steps into another TeamProject. If you have the same Work Item Type Definitions in both projects, you don't need to create field mappings.
Another option would be to use Excel as "Export" and "Import" cache, but you might loose some information, because not everything could be shown in Excel, e.g. Steps of a TestCase, the history, Work Item Links.
If you are skilled in programming using TFS API, you could write your own small migrator, but this could be a lot of effort.
All in all the TFS Integration Platform should be the easiest and best way, so what have been your expectations that have not been fulfilled?
You can use an alternative methods.
First export all Test cases using "Test case extractor."
Them import them in new project using "Test case import tool."
Adding to the point mentioned above, for exporting the test cases you might find the below link more useful:
http://tfstestcaseexporttoexcel.codeplex.com/
I have given it a try and found it very useful and easy to use.
I installed the Basic TFS trial version and now it got expired.
It is mandatory for me to get the history of TFS.
Where does it store the history? Does it store it in the SQL Express?
Is there any way to get the saved history?
Digging through the database is not trivial. You'd have to piece the history back together and de-deltify all the blogs.
It would be much easier just to get your TFS instance working again so that you can get the files out of it. TFS Express 2012 is now available, and has no such time restriction. It's free for up to 5 users. You may be able to upgrade your existing installation.
If you are still able to do a get, you could hook up git-tfs. Once you execute the git-tfs clone, you will be able to view the history using git. You can look at this tutorial for more information.
Did you consider trying querying the TFSWarehouse and use and automatic script to recreate history ?
Reference: Export TFS 2010 History to Excel or Text Document
I used to invoke the BuildStore.asmx to get the build info from TFS 2008, such as work items, build steps, change set, etc.
But recently, our project moved to TFS 2010. And the BuildStore.asmx is deprecated. TFS 2010 offers a new object model to provide these info.
So, in order to minimize the code change, I want to know the counterparts in TFS2010. Thanks for any hints.
I found some info about the build API in TFS, such as:
http://blogs.msdn.com/b/buckh/archive/2006/09/14/getbuilduri-getbuilddetails.aspx
But they are mainly about TFS2008.
You can make use of direct service-calls. The counterpart you re looking for should reside under "http://TfsName:Port/tfs/TeamCollectionName/Build/v3.0/BuildService.asmx".Another, possibly far more efficient, approach is to write code against TFS-SDK, which should 'survive' from TFS-version to TFS-version. There are numerous resources out there regarding material, this article by S. Raiten seems to be a good jump-start.
I just found some useful material:
http://social.msdn.microsoft.com/Forums/en-AU/tfsgeneral/thread/92766815-c09b-422b-91fc-5e745e3aaa21
Currently our build solution is set up using TFS + MS Build scripts.
TFS is also being used as a CI server.
I've seen several posts on this site telling people about other CI solutions.
Are there any compelling options to move to another Solution for our build system?
Or in other words what are we missing out on by using TFS?
EDIT
We are using TFS for source control / issue tracking and I think this is a good solution, im just wondering about the other options for build server / CI server integrating with TFS.
The main problem with TFS is that if you have a server crash, restoring your source code is non-trivial. This is unbelievably bad since the most important aspect of any source control system must be to be fail-resistent, at least if you perform all backups as you should.
IMHO the greatest benefit of TFS is that everything is integrated in the IDE: work items, bug tracking, CI, Code analysis, ...
I have used TFS in the past but my current company use SubVersion/Team City/FogBugz to implement the same functionality provided in the TFS solution.
I would say that from a technical implementation perspective, you can gain additional features from a non-TFS system that TFS would be a nightmare to configure.
However, that said, one of the biggest reasons for not going for TFS is the cost of running such a system. The big advantage of TFS is the integration of everything which makes people use it more as the more you put in, the more you get out. The worst case scenario is a system that people can’t be bothered using which adds no value to the company’s development.
In my opinion, if you are already on TFS and can afford to stick with do, do just that!