(anonymous) wrote:
[...]
> JIRA however is much more complicated. You know
from your own
> experience (
https://jira.toolserver.org/browse/TS-748 has now been
> unresolved for over three years) that few of the Toolserver admins
> have time and knowledge with regard to JIRA, while in the WMF camp
> they have probably zero. So compared with MediaWiki where
> (security) updates will be regularly deployed with the rest of the
> cluster, someone would have to keep a dedicated eye on a totally
> foreign sys- tem. And we only have a free licence from Atlassian
> which could at some point be discontinued. On the other hand the
> benefits are very small as Merlijn wrote the fantastic JIRA/
> Bugzilla importer which handles almost all cases.
Yes I know those issues... ;) It is/was a pitty...
As far as I know, the JIRA/Bugzilla importer has
issues as well,
please confer
https://bugzilla.wikimedia.org/show_bug.cgi?id=55673.
It does e.g. NOT preserve relations between tickets and thus
drops a serious amount of the history too. As I understand from
the buzilla ticket this will not be resolved.
In my oppinion 1 of the 2 problems should be
tackeled;
* either keep a static copy of JIRA (may be just the DB along with
a simple viewer written by us)
* or improve JIRA/Bugzilla importer to a point where it can
migrate relations between tickets and other stuff as well
As I wrote last month in
http://permalink.gmane.org/gmane.org.wikimedia.toolserver/6450,
you can export an XML dump of your project's issues (you'll
have to download attachments manually (or write a script for
that)). This contains the links between issues. You can
then store it in your software's repository or any other
place and convert it to HTML, wiki pages, a book or one of
those bubble movies - the world is your oyster.
Tim