<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid:38EA208F-1077-4250-9864-AAD1887B589D@redhat.com"
type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I'm a jira admin - what do you want ? ;)
If you want old links to work I assume we need to create WELD and
move all WB issues to it.
</pre>
</blockquote>
<pre wrap="">Yep that's pretty much it I think,
</pre>
</blockquote>
<pre wrap=""><!---->
But it does involve reopening all old issues. If you can do this, and
make sure all the state is maintained fine, otherwise we need to do
this at the DB level (which involves breaking old links).
</pre>
</blockquote>
Ah yes - I forgot about that limitation.<br>
<br>
I suggest we simply move any *moveable* issues over via bulk
manipulation and just leave the non-moveable (closed ones) in the WB*
projects.<br>
<br>
That keeps the links working and the jira actually reflect what
changed/happend.<br>
<blockquote cite="mid:38EA208F-1077-4250-9864-AAD1887B589D@redhat.com"
type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">plus the notifications sent to the weld-issues list. If you're able
to sort this out, then I'll let the help desk guys know that they
don't need to do it.
</pre>
</blockquote>
<pre wrap=""><!---->
If you can update the notification scheme, that would be great.
</pre>
</blockquote>
Yes - all done.<br>
<br>
/max<br>
</body>
</html>