Community
Participate
Working Groups
While tracking down a problem with a Jira plugin, I sniffed the packet exchange between Mylyn/Eclipse and Jira, and discovered the following pattern: From JIRA to MYLYN: ... <description xsi:type="soapenc:string">Testing 123</description> ... <values xsi:type="soapenc:string">0018000000lL2qfAAC</values> ... From MYLYN to JIRA: ... <values xsi:type="xsd:string">Testing 456</values> ... <values xsi:type="xsd:string">[0018000000lL2qfAAC]</values> From JIRA to MYLYN: ... <description xsi:type="soapenc:string">Testing 456</description> ... <values xsi:type="soapenc:string">[0018000000lL2qfAAC]</values> ... Note that the only field I changed in Eclipse was the description field (from "Testing 123" to "Testing 456"). The custom field value (of type "soapenc:string") was sent as "0018000000lL2qfAAC", but was returned as "[0018000000lL2qfAAC]". To reproduce this bug: add a custom field to a Jira issue, set to an alphanumeric value, sync the issue to Mylyn, change the description, sync the issue back to Jira. This issue appears to be caused by the XML encoding/decoding process. More extensive packet traces are posted on this forum thread: http://forums.atlassian.com/thread.jspa?messageID=257360148
The Mylyn JIRA Connector has moved to Atlassian. Please file this bug and all future reports at: https://studio.atlassian.com/browse/PLE . Please see this FAQ entry for further details: http://wiki.eclipse.org/Mylyn/FAQ#What_happened_to_the_Mylyn_JIRA_Connector.3F .