Bug 302681 - Stacked bar charts are not sorting on optional y series grouping correctly
Summary: Stacked bar charts are not sorting on optional y series grouping correctly
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 2.5.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Birt-Chart-inbox@eclipse.org CLA
QA Contact: Xiaoying Gu CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-12 04:21 EST by john mcteague CLA
Modified: 2013-09-10 23:06 EDT (History)
4 users (show)

See Also:


Attachments
Attached report show the problem (51.21 KB, application/octet-stream)
2010-02-12 04:21 EST, john mcteague CLA
no flags Details
Image of report (108.72 KB, image/jpeg)
2010-02-12 04:24 EST, john mcteague CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description john mcteague CLA 2010-02-12 04:21:03 EST
Build Identifier: BIRT Engine version 2.5.1.v20090916

Stacked bar chart with multiple values. The optional Y series grouping is a string value but data sorting is on an integer value descending. The values in the bar are not sorted by volume, there appears to be some sort of ordering being applied, but it is not accurate.

Reproducible: Always

Steps to Reproduce:
See attachement
Comment 1 john mcteague CLA 2010-02-12 04:21:49 EST
Created attachment 158961 [details]
Attached report show the problem
Comment 2 john mcteague CLA 2010-02-12 04:24:29 EST
Created attachment 158962 [details]
Image of report

The attached image shows that for the Aug-08 bar, the first 7 entries are sorted correctly, but then the value 3217 appears out of order.

What can be seen is that the entries seem to be in the same order for each bar, although they should be sorted differently.
Comment 3 Yulin Wang CLA 2010-02-20 00:36:19 EST
(In reply to comment #2)
> Created an attachment (id=158962) [details]
> Image of report
> 
> The attached image shows that for the Aug-08 bar, the first 7 entries are
> sorted correctly, but then the value 3217 appears out of order.
> 
> What can be seen is that the entries seem to be in the same order for each bar,
> although they should be sorted differently.

Currently sorting key of optional grouping is based on aggregation values. That means the aggregated values are used to determine the order, rather than single value in each category. In this case 3210+17 is less than other values such as 1622+1622. 
This is expected behavior, but I agree the values in each category should be sorted respectively. However this is difficult to implement this behavior, so defer to future to see if feasible.
Comment 4 Hagen Rahn CLA 2013-09-10 23:06:59 EDT
Although I'm aware that this bug-report has not been visited for a while I really would like to see any progress on this as there are two major releases in between (I'm using Version: 4.3.0.v201306051647-8F8y79FT0z0-U-C15CS3sN Build id: v20130611-1045).

My proposal would be to sort the legend according the aggregated values and the stacked columns according the column specific sort order.