blocks|key|4836150|text|我不认为有一种简单的方法来做你想做的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4836151|我认为您需要使用TFS+API制作自己的工具。我不知道JIRA是否有执行插入的API，但TFS的api相当不错。你可以很容易地把这些数据拿出来。|4836152|对于TFS上的“如何操作”，我通常会选择Shai+Raitan's+TFS+API+blog+posts。|offset|length|4836153|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.microsoft.co.il/blogs/shair/archive/tags/TFS%2BAPI/default.aspx^0|0|0|K|W|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I don't think there is an easy way to do what you want.

I am thinking you would need to make your own tool using the TFS API. I don't know if JIRA has an API to do the inserting, but TFS's api is fairly good. You could easily get that data out.

For "How To" on the TFS API I usually look to <a href="http://blogs.microsoft.co.il/blogs/shair/archive/tags/TFS+API/default.aspx" rel="noreferrer">Shai Raitan's TFS API blog posts</a>.

blocks|key|4836202|text|我做从各种数据库(ClearQuest、TeamTrack、Remedy)到JIRA的自定义迁移。这项工作大约需要一周的时间，所以价格并不便宜，但如果你有很多数据，想要比标准进口商提供的信息更多的信息，这是一种方法。CSV导入器可能不会执行您想要的操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4836203|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I do custom migrations from all sorts of databases (ClearQuest, TeamTrack, Remedy) into JIRA. It takes about a week to do the job so it isn't cheap but if you have a lot of data and want more information than the standard importers provide, it's one way to go. The CSV importer probably won't do what you want.

blocks|key|1934836|text|看看Appfire's+Enterprise+Migration+Utility吧。它将TFS迁移到JIRA等。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1934837|entityMap|0|LINK|mutability|MUTABLE|url|https://plugins.atlassian.com/plugins/com.appfire.jira.plugins.appfire-enterprise-migration-utility^0|2|12|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Have a look at <a href="https://plugins.atlassian.com/plugins/com.appfire.jira.plugins.appfire-enterprise-migration-utility" rel="nofollow">Appfire's Enterprise Migration Utility</a>. It migrates TFS to JIRA, amongst others.

blocks|key|4836267|text|很简单，创建一个包含所有工作项的查询，单击图标在Excel中打开，将Excel文件另存为CSV。好了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4836268|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Simple enough, create a Query that has all your work items, click on the icon to open in Excel, 
Save the Excel file as CSV. 
done.

blocks|key|4836372|text|下面是对我有效的方法(很抱歉，这是一个.docx)：对于每个TFS+Server：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4836373|使用迭代路径为所有产品待办事项创建查询，为每个产品和/或每个Scrum团队创建Bug。|4836374|通过更改迭代路径，可以将单个查询用于所有项目/产品|4836375|通过选择适当的列来格式化TFS中的结果。|4836376|保存查询，运行查询，然后在Excel中打开包含单词RAW的.xlsx文件(例如，XXXX_ALL_WIs_RAW.xlsx)。|4836377|使用相同的文件，选择另存为…若要创建和保存excel+.csv文件，请执行以下操作。|4836378|请注意，并不是所有的列/映射都将用于所有项目。删除不必要的列，并根据需要更改列标题。|4836379|对于我来说，TFS列/字段以及它们映射到的Jira字段(一些自定义的)是：|4836380|迭代路径映射到Scrum团队|4836381|ID映射到旧ID|4836382|工作项类型映射到问题类型|4836383|标题映射到摘要|4836384|描述映射到描述|4836385|验收标准映射到验收标准|4836386|Assigned+To+map+to+Assignee+(用户必须存在于Jira中才能正常工作！)|4836387|SubCategory映射到组件|4836388|努力映射到故事点|4836389|严重性映射到优先级|4836390|案例编号映射到案例ID|4836391|客户名称映射到客户|4836392|平台映射到环境|4836393|修改.csv后，使用文件/检查问题/检查文档来确定是否需要修改，以便检查结果不会产生任何问题。|4836394|将干净的.csv另存为_CLEAN+(例如，XXXX_ALL_WIs_CLEAN.csv)。|4836395|将要导入的电子表格标题重命名为适当的Jira字段名称。|4836396|字段修改：|4836397|如果work+item+Acceptance字段中没有任何内容，请在csv上输入“No+Acceptance+in+the+original+TFS+work+item”。|4836398|如果工作项描述字段中没有任何内容，请在csv上输入“No+Description+in+the+original+TFS+work+item”。|4836399|Bugs+-必须将严重性转换为一个数字(1到5)。|4836400|更改.csv上的列标题以匹配Jira字段名，如上面在2d中定义的那样。|4836401|清理/检查.csv|4836402|如有必要，适当增加Jira中的高级设置jira.bulk.create.max.issues.per.import，以处理要导入的项目数量(默认情况下有250个项目导入限制)。|4836403|在Jira中，在站点管理员级别-基于单个产品创建新的Jira项目(而不是项目！)|4836404|创建或添加将在各种项目中使用的用户。|4836405|在Jira中，在站点管理员级别-根据需要创建自定义字段|4836406|将新的和现有的自定义字段与相应的项目屏幕相关联，并更新。|4836407|在Jira中，在站点管理员级别-重新索引数据库|4836408|在项目级别-使用TFS中的子类别为产品创建组件。(可分配给组件引线)|4836409|现在您应该已经准备好导入到Jira中。|4836410|测试用例从TFS迁移到Jira/Zephyr+(如果您需要的话)：|4836411|测试用例迁移是一个由两部分组成的过程。第一部分将从TFS获取测试用例，并创建并格式化包含数据的Excel电子表格，然后将数据导入Jira+(Zephyr)。流程的第二部分将使用Java工具从流程的第一部分中创建的电子表格中导入数据。|4836412|第1部分-测试用例导出|4836413|4836414|Install+TCExport+(用于创建电子表格，用于将测试用例导入到Zephyr中)。|ordered-list-item|4836415|在使用.jar工具映射字段时，请使用Excel列字母。|4836416|4836417|第2部分-测试用例导入1.下载导入实用程序zfj-importer-+utility+-0.38.jar|4836418|4836419|在大多数环境中，可以通过双击文件来运行此实用程序。要启动该实用程序，请双击.jar文件或通过命令提示符运行：https://www.getzephyr.com/insights/getting-started-zephyr-jira-importer-utility|offset|length|4836420|+-jar。有关使用该实用程序的详细说明，请访问以下地址:+java+|4836421|unordered-list-item|4836422|4836423|entityMap|0|LINK|mutability|MUTABLE|url|https://www.getzephyr.com/insights/getting-started-zephyr-jira-importer-utility^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|1I|27|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|3A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|3B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|3C|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|3D|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|3E|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|3F|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|3G|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|3H|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|3I|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|3J|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|3K|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|3L|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|3M|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|3N|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|3O|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|3P|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|3Q|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|3R|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|3T|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3U|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|3V|8|@]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|3W|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|3X|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|6|7|3Y|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|6|7|3Z|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|6|7|40|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|6|7|41|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|42|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|6|7|43|8|@]|9|@]|A|$]]|$1|1X|3|1Y|5|6|7|44|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|6|7|45|8|@]|9|@]|A|$]]|$1|21|3|22|5|6|7|46|8|@]|9|@]|A|$]]|$1|23|3|24|5|6|7|47|8|@]|9|@]|A|$]]|$1|25|3|26|5|6|7|48|8|@]|9|@]|A|$]]|$1|27|3|28|5|6|7|49|8|@]|9|@]|A|$]]|$1|29|3|2A|5|6|7|4A|8|@]|9|@]|A|$]]|$1|2B|3|2C|5|6|7|4B|8|@]|9|@]|A|$]]|$1|2D|3|2E|5|6|7|4C|8|@]|9|@]|A|$]]|$1|2F|3|2G|5|6|7|4D|8|@]|9|@]|A|$]]|$1|2H|3|2I|5|6|7|4E|8|@]|9|@]|A|$]]|$1|2J|3|-4|5|6|7|4F|8|@]|9|@]|A|$]]|$1|2K|3|2L|5|2M|7|4G|8|@]|9|@]|A|$]]|$1|2N|3|2O|5|2M|7|4H|8|@]|9|@]|A|$]]|$1|2P|3|-4|5|6|7|4I|8|@]|9|@]|A|$]]|$1|2Q|3|2R|5|6|7|4J|8|@]|9|@]|A|$]]|$1|2S|3|-4|5|6|7|4K|8|@]|9|@]|A|$]]|$1|2T|3|2U|5|2M|7|4L|8|@]|9|@$2V|4M|2W|4N|1|4O]]|A|$]]|$1|2X|3|2Y|5|6|7|4P|8|@]|9|@]|A|$]]|$1|2Z|3|-4|5|30|7|4Q|8|@]|9|@]|A|$]]|$1|31|3|-4|5|6|7|4R|8|@]|9|@]|A|$]]|$1|32|3|-4|5|6|7|4S|8|@]|9|@]|A|$]]]|33|$34|$5|35|36|37|A|$38|39]]]]

Here's what worked for me (sorry about the formatting; it was a .docx):
For every TFS Server:

Create a query by using Iteration Path for all Product Backlog Items and Bugs for every Product and/or every Scrum Team.

A single query can be used for all projects/products by altering the iteration path(s)

Format the results in TFS by selecting the appropriate columns.

Save the query, run it, and open it in Excel an .xlsx file with the word RAW included (for example, XXXX_ALL_WIs_RAW.xlsx).

Using the same file, select Save As… to create and save an excel .csv file.

Note that not all columns/mappings will be used on all projects. Delete unnecessary columns, and change column headings as needed. 

The TFS columns/fields, and the Jira fields (some custom) to which they are mapped, for me were:

Iteration Path maps to Scrum Team

ID maps to Legacy ID

Work Item Type maps to Issue Type

Title maps to Summary

Description maps to Description

Acceptance Criteria maps to Acceptance Criteria

Assigned To maps to Assignee (Users must exist in Jira for this to work!)

SubCategory maps to Component/s

Effort maps to Story Points

Severity maps to Priority

Case Number maps to Case ID

Client Name maps to Customer

Platform maps to Environment

Once the .csv has been modified, use File/Check for Issues/Inspect document to determine if modification are required so the inspection results yield no issues.

Save the clean .csv as _CLEAN (for example, XXXX_ALL_WIs_CLEAN.csv).

Rename spreadsheet headers for import to appropriate Jira field names.

Field modifications:

If the work item Acceptance Criteria field has nothing in it, enter “No Acceptance Criteria in the original TFS work item” on the csv.

If the work item Description field has nothing in it, enter “No Description in the original TFS work item” on the csv.

Bugs – Severity must be converted to a number (1 through 5).

Change column headings on the .csv to match the Jira field names, as defined above in 2d.

Clean/Inspect the .csv

If necessary, increase the advanced setting jira.bulk.create.max.issues.per.import in Jira appropriately to handle the number of items being imported (there is a 250 item import limit by default).

In Jira, at the Site Admin Level – Create new Jira projects based on individual products (NOT projects!) 

Create or add users that will be used in the various projects.

In Jira, at the Site Admin level – Create Custom Fields as needed

Associate new and existing custom fields to appropriate project screens, and update.

In Jira, at the Site Admin Level – Re-index DB

At the Project level – Create components for the product by using subcategory from TFS. (Can be assigned to Component Lead)

You should now be ready for import into Jira.

Test Case Migration from TFS to Jira/Zephyr if you need it:

Test case migration is a 2-part process. 
The first part will get the test cases from TFS, and create and format an Excel spreadsheet containing the data that will then be imported into Jira (Zephyr). 
The second part of the process will use a Java tool to import the data from the spreadsheet created in Part 1 of the process.

Part 1 – Test Case Export

<ol>
<li>Install TCExport (Used to create the Excel spreadsheet that will be used to import the test cases into Zephyr). </li>
<li>When mapping fields while using the .jar tool, use the Excel column letter.</li>
</ol>

Part 2 – Test Case Import
1. Download the import utility zfj-importer-utility-0.38.jar 

<ol start="2">
<li>This utility can be run by double-clicking the file in most environments. To launch the utility double-click the .jar file or run through the command prompt as: java -jar .</li>
<li>Detailed instructions for using the utility can be found here: <a href="https://www.getzephyr.com/insights/getting-started-zephyr-jira-importer-utility" rel="nofollow noreferrer">https://www.getzephyr.com/insights/getting-started-zephyr-jira-importer-utility</a></li>
</ol>

I am in the process of evaluating JIRA as a replacement to TFS 2010.
I know that JIRA has the capability to import from CSV but cannot figure out how to export fields like the History fields from TFS to a spreadsheet.

Any recommendations / tools would be highly appreciated.

What would be the best way to migrate work items from TFS 2010 to JIRA?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在评估JIRA作为TFS2010的替代品。我知道JIRA能够从CSV导入，但不知道如何将历史字段等字段从TFS导出到电子表格。任何建议/工具都将受到高度赞赏。

问将工作项从TFS2010迁移到JIRA的最佳方式是什么？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将工作项从TFS2010迁移到JIRA的最佳方式是什么？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将工作项从TFS2010迁移到JIRA的最佳方式是什么？
EN