AdHoc action output expressions cannot access inputs or task/workflow context

Bug #1761829 reported by Bob Haddleton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
In Progress
Medium
Bob Haddleton

Bug Description

When using expressions in an AdHoc action output definition, the expressions only have access to the content of the result of the action, they cannot reference data that is in the inputs or task/workflow context. This makes it difficult to do data transformation in the output that may require information from the inputs or other context.

Changed in mistral:
assignee: nobody → Bob Haddleton (bob-haddleton)
status: New → In Progress
Dougal Matthews (d0ugal)
Changed in mistral:
importance: Undecided → Medium
Dougal Matthews (d0ugal)
Changed in mistral:
milestone: none → rocky-2
Dougal Matthews (d0ugal)
Changed in mistral:
milestone: rocky-2 → rocky-3
Dougal Matthews (d0ugal)
Changed in mistral:
milestone: rocky-3 → stein-1
Dougal Matthews (d0ugal)
Changed in mistral:
milestone: stein-1 → stein-2
Changed in mistral:
milestone: stein-2 → stein-3
Changed in mistral:
milestone: stein-3 → train-1
Changed in mistral:
milestone: train-1 → ussuri-1
Changed in mistral:
milestone: ussuri-1 → ussuri-2
Changed in mistral:
milestone: ussuri-2 → ussuri-3
Changed in mistral:
milestone: ussuri-3 → victoria-1
Changed in mistral:
milestone: victoria-1 → wallaby-1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.