Sets the component(s) that you want to limit your report to
include. Multiple values can be separated by commas (such as
10011,10012). If this is set to empty - that means all components
will be included.

Sets the fix version id(s) that you want to limit your report to
include. These are JIRA's internal version ids, NOT the
human readable display ones. Multiple fix versions can be separated
by commas. If this is set to empty - that means all fix versions
will be included.

Report output directory. Note that this parameter is only relevant
if the goal is run from the command line or from the default build
lifecycle. If the goal is run indirectly as part of a site
generation, the output directory configured in the Maven Site
Plugin is used instead.Default value is: ${project.reporting.outputDirectory}.

Report output encoding. Note that this parameter is only relevant
if the goal is run from the command line or from the default build
lifecycle. If the goal is run indirectly as part of a site
generation, the output encoding configured in the Maven Site Plugin
is used instead.Default value is: ${project.reporting.outputEncoding}.

Sets the priority(s) that you want to limit your report to include.
Valid statuses are Blocker, Critical,
Major, Minor and Trivial.
Multiple values can be separated by commas. If this is set to empty
- that means all priorities will be included.

Sets the column names that you want to sort the report by. Add
DESC following the column name to specify
descending sequence. For example Fix Version DESC,
Type sorts first by the Fix Version in descending order and
then by Type in ascending order. By default sorting is done in
ascending order, but is possible to specify ASC for
consistency. The previous example would then become Fix
Version DESC, Type ASC.

Note: If you are using JIRA 4 you need to put
your sort column names in the reverse order. The handling of this
changed between JIRA 3 and JIRA 4. The current default value is
suitable for JIRA 3. This may change in the future, so please
configure your sort column names in an order that works for your
own JIRA version.

Sets the types(s) that you want to limit your report to include.
Valid types are: Bug, New Feature,
Task, Improvement, Wish,
Test and Sub-task. Multiple values can be
separated by commas. If this is set to empty - that means all types
will be included.

If you have a project in JIRA with several components that have
different release cycles, it is an often used pattern to prefix the
version with the name of the component, e.g. maven-filtering-1.0
etc. To fetch issues from JIRA for a release of the
"maven-filtering" component you would need to set this parameter to
"maven-filtering-".

Sets the component(s) that you want to limit your report to
include. Multiple values can be separated by commas (such as
10011,10012). If this is set to empty - that means all components
will be included.

Sets the fix version id(s) that you want to limit your report to
include. These are JIRA's internal version ids, NOT the
human readable display ones. Multiple fix versions can be separated
by commas. If this is set to empty - that means all fix versions
will be included.

Report output directory. Note that this parameter is only relevant
if the goal is run from the command line or from the default build
lifecycle. If the goal is run indirectly as part of a site
generation, the output directory configured in the Maven Site
Plugin is used instead.

Report output encoding. Note that this parameter is only relevant
if the goal is run from the command line or from the default build
lifecycle. If the goal is run indirectly as part of a site
generation, the output encoding configured in the Maven Site Plugin
is used instead.

Sets the priority(s) that you want to limit your report to include.
Valid statuses are Blocker, Critical,
Major, Minor and Trivial.
Multiple values can be separated by commas. If this is set to empty
- that means all priorities will be included.

Sets the column names that you want to sort the report by. Add
DESC following the column name to specify
descending sequence. For example Fix Version DESC,
Type sorts first by the Fix Version in descending order and
then by Type in ascending order. By default sorting is done in
ascending order, but is possible to specify ASC for
consistency. The previous example would then become Fix
Version DESC, Type ASC.

Note: If you are using JIRA 4 you need to put
your sort column names in the reverse order. The handling of this
changed between JIRA 3 and JIRA 4. The current default value is
suitable for JIRA 3. This may change in the future, so please
configure your sort column names in an order that works for your
own JIRA version.

Sets the types(s) that you want to limit your report to include.
Valid types are: Bug, New Feature,
Task, Improvement, Wish,
Test and Sub-task. Multiple values can be
separated by commas. If this is set to empty - that means all types
will be included.

If you have a project in JIRA with several components that have
different release cycles, it is an often used pattern to prefix the
version with the name of the component, e.g. maven-filtering-1.0
etc. To fetch issues from JIRA for a release of the
"maven-filtering" component you would need to set this parameter to
"maven-filtering-".