Allows the output file to be placed anywhere on the file system

-e #budget will result in no budget values in the output -- yet the Budget heading is there

• I had to upgrade to Gradle version 7.4.2 because of a class file incompatibility problem
• The Google Java formatting plugin then failed with "missing annotations"

I got the build to work by disabling the Google Java Formatting plugin in the build.gradle file.

@sjamesr may be interested

It would be nice to have hyperlinks in the report to allow viewing of the source issue on GitHub

@sjamesr might be interested

when a from and a to date are specified, issues with no comments should not be included in the PDF

It would be very useful to allow the user to capture specific values into a comment and have them extracted for later use. This new feature would promote applications such as budgeting, project planning, scheduled maintenance alerting.

Budgeting

Often we need to allocate a budget to an issue, especially for high cost issues. The user would enter a "hash tag" with an associated value. For example

• The expected cost is #Budget=$15,000
• Acme enterprises provided #Quote=$12,500

Values of this kind would be extracted to a CSV file output along with the PDF report

Issue no,Issue name,Date,Budget,Quote
45,Sandblast the hull,1/3/23,15000,
45,Sandblast the hull,4/3/23,,12500

Time management

Under a routine or regular maintenance issue we might want to capture the next service date. For example under 123 -- Service outboard moter the comment might be:

23/4/23 -- Outboard serviced at Acme Motors Pty Ltd, #NextDueDate=23/4/24

The CSV output would be

Issue No,Issue,Date,NextDueDate
123,Service Outboard Motor,23/4/23,23/4/24

Another application could take this output and create a calendar entry as a reminder when service is due

Other metrics

Other values can be captured using hashtags. For example, issue 124 -- Service main engine at 250hr intervals we might record when service are done and when they are next due by entering a comment:

15/6/23 -- Engine service by Acme Motors Pty Ltd at The Boatworks #EngineHours=34922, #NextDueHours=3650

The CSV output would be

Issue No,Issue,Date,EngineHours,NextDueHours
124,Service main engine at 250hr intervals,15/6/23,3422,3650

Another application may compare this output with the #CurrentEngineHours value (reported from another issue comment or via on board sensor data) and create an alert when engine service is near due (or overdue)

Database of known tags

A file called hash_tags would store a list of valid hash tags along with the regular expression defining the format of the value to be extracted. For example

EngineHours \d*
NextDueHours \d*
NextDueDate \d\d/\d[\d]/\d\d[\d\d]
#Budget ^\$[0-9]*

This happens when the budget value is part of the issue "body" -- the text entered when creating the issue