Currently, Bamboo offers use of global and Plan level variables - accessible in scripts either as ${bamboo.<variable_name>} or $bamboo_<variable_name>. In addition, script tasks can take input arguments accessible (within script) as $1, $2, etc.

At first, I thought that it would be good to have ability to define NAMED SCRIPT ARGUMENTS (see BSP-40324: https://getsupport.atlassian.com/servicedesk/customer/portal/10/BSP-40324), but then - a better idea has come up: JOB and TASK level variables.

Ability to define JOB level variables (similar to Plan variables) - would make these variables available to all tasks within that job (accessible as ${<variable_name>} or ${job.<variable_name>}. Same for TASK level variables (accessible as ${<variable_name>} or ${task.<variable_name>}) - except these would only be available to a single task.

In a sense, both JOB and TASK level variables - would satisfy NAMED ARGUMENTS request submitted in BSP-40324.