Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342367

Summary: order of custom fields changes depending on whether values are set or not
Product: z_Archived Reporter: Steffen Pingel <steffen.pingel>
Component: MylynAssignee: Frank Becker <eclipse>
Status: RESOLVED FIXED QA Contact: Frank Becker <eclipse>
Severity: normal    
Priority: P3 CC: robert.elves, sam.davis
Version: unspecified   
Target Milestone: 3.6   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
patch V1
none
mylyn/context/zip none

Description Steffen Pingel CLA 2011-04-10 10:16:42 EDT 
When a repository defines custom fields the order of these can vary when tasks are opened in the editor. Looking at the XML output for Bugzilla tasks only custom fields that have values are listed. When Bugzilla initializes task data custom fields are added as they are received since they are not pre-defined in BugzillaClient.setupExistingBugAttributes(). When all data for a bug has been received SaxMultiBugReportContentHandler.endElement() adds attributes that didn't have a value set resulting in a different order for different tasks. 

To fix this the Bugzilla connector should always initialize task data with known custom fields.
Comment 1 Frank Becker CLA 2011-04-29 16:00:15 EDT 
Created attachment 194404 [details]
patch V1

committed patch
Comment 2 Frank Becker CLA 2011-04-29 16:00:17 EDT 
Created attachment 194405 [details]
mylyn/context/zip
Comment 3 Frank Becker CLA 2011-04-29 16:02:17 EDT 
Steffen

can you please verify and reopen if you found a problem.