[#REPOR-102] Using format parameter on (relative) date filter causes Unparseable date error

Confluence Extension: Reporting Plugin

Using format parameter on (relative) date filter causes Unparseable date error

Created: 20/Nov/07 12:43 AM Updated: 04/Mar/08 03:12 AM

Component/s:

{content-reporter}

Affects Version/s:

1.3.2

Fix Version/s:

2.0.0

Time Tracking:

Not Specified

Description

« Hide

date-filter: java.text.ParseException: Unparseable date: "-1d"

is thrown by the following report:

{report-block}
 {content-reporter:space=@self|types=+page|scope=This page> children}
  {date-sort:data:item-inceptiondate|order=descending}
   {date-filter:data:item-inceptiondate|maxValue=4w|minValue=-1d|format=dd MMM yyyy}
{content-reporter}
{report-body}
* {report-info:content:title|link=true} - {report-info:data:item-inceptiondate|format=dd MMM yyyy}
{report-body}
{report-empty}_No items to report._{report-empty}
{report-block}

The format=dd MMM yyy is used on the template for the pages being reported on. The instructions clearly state that the format parameter should be used when using maxValue/minValue, however this doesn't appear to be true when using a period like "2d" or "2w".

Maybe it's just the documentation that needs updating!

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

David Peterson added a comment - 05/Feb/08 02:04 AM

I'll check if it's just documentation or code which needs to be fixed. I think it should allow the format to be specified but still use relative dates, since you may want to mix a fixed date with a relative one (eg. fix the minDate but have a relative date for the maxDate), which would require a format to be specified.

[ Permalink | « Hide ]

Nick Waanders added a comment - 05/Feb/08 02:28 AM

In that case I think it certainly is a documentation issue - I'm using mostly relative dates & hadn't thought of mixing the two types!

Nick

[ Permalink | « Hide ]

David Peterson added a comment - 04/Mar/08 03:12 AM

This has been fixed so that an error is not display, the min and max values work as expected, and the documentation has been updated to be clearer on the requirements.