On 9 Mar 2015 18:22, "Alan Williams" <[email protected]> wrote:
> Maybe need component for server. Also, where would command line tool issues go? Sorry, I think only the moved components with issues show up there. See http://jira.s11.no/browse/TAVERNA/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel for all. (I did not move the Server issues from T3 to TAVERNA here as I thought I had to fill the gap in numbering - turns out the numbers are shuffled anyway :-( ) > 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. Yes, for take #2 perhaps you could go through each activity component in the old JIRA and bulk change to add the corresponding label.? Otherwise some of the bugs might be confusingly incomplete, like "XML error" > 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. Yes, we can shuffle around components as we please. >> 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? Links seems to work as long as the links are within the moved issues. Not so sure about links in comments. > Will it help if we go through the "None" Components before the real move? No, let's move first.
