Bug #23344
closed
In "Run Workflow" action, "Project where the workflow will run" is ignored
Description
When running a workflow from the `/workflows/...` the user can specify where the workflow should be executed, but this is ignored. Instead, the workflow (container_request) always runs in the place where the workflow definition is stored.
Updated by Brett Smith 4 months ago
- Release set to 83
- Subject changed from Workflows executed from the Workflow view are always running in the same place to Workflows executed from the Workflow ignore "Run in project" selection
Confirmed in 3.2.0.
Updated by Brett Smith 4 months ago
- Subject changed from Workflows executed from the Workflow ignore "Run in project" selection to In "Run Workflow" action, "Project where the workflow will run" is ignored
Updated by Brett Smith 4 months ago
- Target version set to Development 2026-01-06
Updated by Brett Smith 3 months ago
- Target version changed from Development 2026-01-06 to Development 2026-01-21
Updated by Stephen Smith 2 months ago
Changes at arvados|7b0928a75de0b02181de7332f70f83c364acf40a branch 23344-run-wf-location-bug
Tests developer-run-tests-services-workbench2: #1673
After tracing all access to the WF run location state, I found that we have a redux form value as well as a redux store value that can be out of sync. The issue is that the project picker often only sets the store value which gets overridden by the redux form value because the picker does a check for originalProject that appears to never evaluate true because originalProject is never set. I removed this check so that the input will always set both values which resolved the issue, and also removed originalProject since it doesn't get used.
- All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
- Tweaked the wf project input to always call input.onchange
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- none
- Code is tested and passing, both automated and manual, what manual testing was done is described.
- passed tests, checked location when running from WF as well as the left panel new button
- The tested code incorporates recent main branch changes.
- yes
- New or changed UI/UX has gotten feedback from stakeholders.
- none
- Documentation has been updated.
- n/a
- Behaves appropriately at the intended scale (describe intended scale).
- no change
- Considered backwards and forwards compatibility issues between client and server.
- none
- Follows our coding standards and GUI style guidelines.
- yes
Updated by
Updated by Stephen Smith 2 months ago
- Status changed from In Progress to Resolved