On 09-Mar-15 17:19, Stian Soiland-Reyes wrote:
I tested out the move.. it seems fairly easy - except for preserving
the keys where I have to be careful.
Example of what I think we should end up with - with the new
components that relate to the git repositories
http://jira.s11.no/browse/TAVERNA
Looking good :)
Maybe need component for server. Also, where would command line tool
issues go?
Is there any way we can tag the (say) WSDL issues with a wsdl label? The
previous Jira probably went overkill with the number of components but
it would be sad to lose the ability to easily find wsdl-related problems.
I'm not sure having a component for Taverna Plugin Component is
worthwhile as the component plugin should be restructured to go into
common activities and workbench common activities. I guess they can be
moved and the Jira component deleted once the restructuring is done though.
but note that I have to do it again with some XML magic or do the Jira
move to TAVERNA-* in production in order for the keys to not be
reassigned. (in a bulk move they are not moved in order! :-( )
How does it manage the links between issues if the keys get reassigned -
or do they get messed up?
Will it help if we go through the "None" Components before the real move?
Alan
