-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: 3.5.3
-
Component/s: Administration - Others
-
Environment:
JDK 1.5.0_06, Windows, Standalone, Microsoft SQL Server
-
3.05
While migrating Issue Tracking data from an old system to JIRA, I noticed that issues that had multiple components specified ended up having no components in JIRA. For example, consider the following jelly:
<jira:CreateIssue project-key="MYP" issueType="Improvement" summary="A big issue" priority="Major" components="A,B,C" assignee="awhitford" reporter="awhitford" description="You know" created="2004-06-27 16:41:21.0" updated="2006-01-04 15:25:03.0" issueIdVar="myIssueID" issueKeyVar="myIssueKey"/>
Despite the attribute called components (plural), it only seems to work if I only mention one component. From browsing the source code, it would appear that it is not sophisticatd enough to detect the string as a list and parse it into an array or collection. Unfortunately, the consequence is that multiple components may not be specified meaning that a manual procedure to "fix up" the data is necessary.