[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: jira conversion - five points

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Sat, 19 Sep 2015 08:03:02 +0200

On 19 September 2015 at 01:27, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Several issues in the jira conversion:
>
> 1. The 'whiteboard' field isn't converted:
> http://subversion.tigris.org/issues/buglist.cgi?status_whiteboard=.&status_whiteboard_type=regexp
> Bert suggests it doesn't need to be.
> Markus points out we could add it to the "issue description" instead of tossing it.
> (I have no strong opinion)
>
I think it's will be very confusing to add status whiteboard as part
of description, given current values of status whiteboard field.
Adding new custom field does worth it also. I suggest just drop it.

> 2. The 'url' field isn't converted. I think it is important: unlike
> 'whiteboard' it can't be derived from the other fields. For example,
> http://subversion.tigris.org/issues/show_bug.cgi?id=4129#desc17 and
> issue #4595 both have links on that field that aren't in any other
> field, and shouldn't be lost. I propose we add the URL (either as
> a custom field, or inline in the Description, whichever is easier)
>
The URL field is already added to Description field. See SVN-4129 for example:
https://issues.apache.org/jira/browse/SVN-4129

> 3. "#desc42" intra-issue and external links will be broken. I suppose
> there is nothing we can do to prevent that, and if we wanted to
> implement a fix, we could do so easily after the migration, too.
>
> 4. Given that an XML export of all issues is only 23MB compressed,
> I think we should archive the final XML export on ASF hardware.
> (Maybe we can just import it to ^/subversion/archive in the repository?)
>
+1, but I'm going to do this after migration when issue tracker on
tigris will be read-only.

-- 
Ivan Zhakov
Received on 2015-09-19 08:03:37 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.