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

Bug 237578

Summary:	[Enhancement] Allow user to define the label for grouping.
Product:	z_Archived	Reporter:	Maggie Shen <lshen>
Component:	BIRT	Assignee:	Xingsheng Zhu <xzhu>
Status:	CLOSED FIXED	QA Contact:	Maggie Shen <lshen>
Severity:	enhancement
Priority:	P3	CC:	bluesoldier, Lionel.wyl
Version:	2.3.0	Keywords:	plan
Target Milestone:	2.5.0 M4
Hardware:	PC
OS:	Windows XP
Whiteboard:	Autoed-All,G

Description Maggie Shen

2008-06-17 23:58:15 EDT

description:
For example, we group by month. So we'd like to display the grouping label as
'2008/04','2008/05','2008/06'...
but now the labels are displayed as 
'2008/04/03','2008/05/05','2008/06/08', which might be the first row of data of the group. We think it's better that user can define the label on his own and the default value could be the first row of data of the group. Maybe we can make it by scripting, but making it by UI operation will be great.

Comment 1 Yulin Wang

2008-06-30 01:48:31 EDT

Need to add format specifier to y optional grouping label

Comment 2 Xingsheng Zhu

2008-10-27 22:50:03 EDT

Fixed. Add an attribute ‘PatternForYOptional’ in SeriesGrouping. And use that attribute to format y-optional grouping label of DateTime or Number type. Also modified the UI.

Comment 3 Xingsheng Zhu

2008-11-19 23:38:57 EST

Re-fix this bug. Added an attribute ‘formatSpecifier’ in legend model. And the formatting of value series legend with Y grouping will use this attribute.
The category legend will use it either instead of using the base series’ format specifier.

Comment 4 Maggie Shen

2008-12-18 04:39:31 EST

A format control is added on the Legend Entries pop-up.(Format Chart->Legend->Entries). The formatting can well resolve the problem when the grouping key is of Date type. But there's also use case if the grouping key is Integer type and the user want to display the label as:

100 - 199
200 - 299
...

Closing this bug and will file another bug if user raises the requirement.