Note: This issue has been discussed on the jira-user list in http://forums.atlassian.com/thread.jspa?threadID=6072&tstart=0 Some reports should allow configuration of the report inside the report page itself. This would allow the user to modify the report params without having to constantly switch back and forth between pages. Example 1: +---

#Config section
Report for group [Atlassian Developers|V]
[X] Show Workload of individual product versions +----
Report Data (remaining workload in days per developer per version)
		Mike	Scott	...
--------------------------------------------
Jira	Version 3.0	14	5
	Version 3.1	6	23 ----------------------+----- ...
Confluence	Version 1.2	26

Example 2 (Version splitting turned off): +---

#Config section
Report for group [Atlassian Developers|V]
[ ] Show Workload of individual product versions +----
Report Data (remaining workload in days per developer)
	Mike	Scott	...
--------------------------------------
Jira	20	28 ----------------------+----- ...
Confluence	26

It is today possible to implement this (see forum thread mentioned above), but it's clumsy, involves duplicating original Jira code, and each plugin developer has do do this for each plugin. A declarative solution would be much easier for the plugin developer, e.g.: <resource type="velocity" name="view" location="templates/plugins/jira/reports/time-tracking-report.vm"> <!-- default would be false --> <property name="allowInlineConfiguration" value="true"/> </resource> Jira would do all the plumbing for the plugin developer (include fields, generate form submission code, etc.). A further improvement suggested by Owen: Might be worth allowing each property to be inlineConfigurable so you can just have some filter that are refined.