This is an idea that would completly change the batch-tasks plugin configuration concept.

Tasks could be configured outside the job's configuration, so that it's own configuration could be independent of the main job configuration.

Here is the behaviour I invisioned:

• Job's configuration should have an option to "Enable Tasks" only.
• After saving the job, a tasks menu should appear in job's left menu that would allow to enter
  task's view like it exists now.
• By entering the Tasks view, while seeing the existing tasks table list, a "New Task" would be shown in the left menu.
• By selection the "New Task" option, we would be shown the same editing fields and behaviour we currently see in the Tasks section, when configuring a job.
• We would edit and saving it returning to the tasks table list.
• In the task configuration, a new option should exist, that would give us the ability to immediatly enable that task in the job's configuration (like a check box). That way we wouldn't need to re-configure the job's after the task is created, just to enable it. Although manually enabling the task must also be possible inside job's configuration.
• Further more, tasks should have exactly the same build environment has the host job, that is, inherit every single environment variable that the build has.

In job's configuration, regarding batch task options, maybe it would be better to have an option only for job's own tasks and another option for called "Tasks from other jobs" or maybe "External Tasks"?

This is an extremely useful plugin! I've noticed it still is in it's embrionary state but it can be improved greatly to give hudson greater flexibility when configuring jobs.

Thanks in advance.