是否有标准的文件格式，用于从问题跟踪器导出问题？ [英] Is there a standard file format for exporting issues from an issue tracker?

问题描述

背景：

我写过备份工具对于要求用户名的Mercurial / Git主机Bitbucket，通过Bitbucket API获取用户的存储库列表，并将它们中的每一个克隆到本地计算机。

Background:
I've written a backup tool for the Mercurial/Git hoster Bitbucket, which asks for a username, gets a list of the user's repositories via the Bitbucket API, and clones each of them to the local machine.

每个Bitbucket存储库都有一个问题跟踪器，现在我有一个新的功能请求：备份问题以及。

Each Bitbucket repository has an issue tracker, and now I've got a new feature request: backup the issues as well.

我可以从Bitbucket API中获得JSON格式的问题。 >
这是一个例子： https：// api。 bitbucket.org/1.0/repositories/christianspecht/bitbucket-backup/issues/

I can actually get the issues in JSON format from the Bitbucket API.
Here is an example: https://api.bitbucket.org/1.0/repositories/christianspecht/bitbucket-backup/issues/

但是如何备份到本地机器？

我可以将JSON保存在文本文件中，但是我不会不要以为JSON格式的问题列表可以做任何有用的事情。

是否有类似标准文件格式的错误/问题？

But how to backup this to the local machine?
I could just save the JSON in a text file, but I don't think you can do anything useful with a list of issues in JSON format.
Is there such a thing like a standard file format for bugs/issues?

在一个完美的世界中，也许是最广泛的问题跟踪系统能够导入的东西？

In a perfect world, maybe anything that the most widespread issue tracking systems are able to import?

推荐答案

我怀疑答案是否定的，没有标准。以下是一些选项：

I suspect the answer is No, there's no standard. Here are some options:

Bugzilla可以导入/导出CSV和XML ：

Bugzilla can import/export both CSV and XML:

这是这个搜索： https://bugzilla.mozilla.org/buglist .cgi？quicksearch = css3 +文本导出为 CSV 和 XML ，这里是这个错误： https://bugzilla.mozilla.org/show_bug.cgi?id=156881 导出为 XML 。

Here's this search: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=css3+text exported to CSV and XML and here's this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=156881 exported to XML.

JIRA可以从Pivotal导入追踪器，Bugzilla，FogBugz，Mantis，Trac等，显然是，并且可以导出为XML和CSV。

JIRA can import from Pivotal Tracker, Bugzilla, FogBugz, Mantis, Trac and more, apparently, and can export as XML and CSV.

这是这个错误： https://jira.atlassian.com/browse/WBS-49 导出为 XML 和此搜索： https://jira.atlassian.com/browse/GHS-5597?jql=text〜导出为 XML 的％22greenhopper％20api％20plugin％22 - 您还可以导出这些作为.xls文件。

Here's this bug: https://jira.atlassian.com/browse/WBS-49 exported as XML and this search: https://jira.atlassian.com/browse/GHS-5597?jql=text~%22greenhopper%20api%20plugin%22 exported as XML - you can also export these as .xls files.

综合管理CLI有一个可以使用的子命令导出创建一堆.csv文件以及包含消息和文件附件的子目录。请参阅 http://roundup.sourceforge.net/docs/admin_guide.html#migrating-后台，了解如何将问题数据迁移到另一个数据库。

The roundup-admin CLI has a sub command export which can be used to create a bunch of .csv files together with sub directories containing the messages and file attachments. See http://roundup.sourceforge.net/docs/admin_guide.html#migrating-backends for how this can be used to migrate the issue data to another database.

Trac可以导出到CSV& TSV。以下是这个搜索： http://trac.edgewall.org/report/2 导出为 CSV 和此错误： http://trac.edgewall.org/ticket/886 导出为 CSV 和 TSV 。

Trac can export to CSV & TSV. Here's this search: http://trac.edgewall.org/report/2 exported to CSV and this bug: http://trac.edgewall.org/ticket/886 exported to CSV and TSV.

这篇关于是否有标准的文件格式，用于从问题跟踪器导出问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！