Bug #21288
closed
Can't launch workflows not in the first 100 list response items
Added by Peter Amstutz 5 months ago.
Updated 3 months ago.
Release relationship:
Auto
Description
Workflow launching gets the a workflow listing but doesn't use paging to get the whole list, so if there are more than 100 items they don't appear. As a result, trying to launch a workflow not in the first 100 items will give a mysterious error "You can't run this process".
- Description updated (diff)
- Target version changed from Future to Development 2024-01-17 sprint
- Assigned To set to Stephen Smith
- Target version changed from Development 2024-01-17 sprint to Development 2024-01-31 sprint
- Assigned To deleted (
Stephen Smith)
- Assigned To set to Lisa Knox
- Target version changed from Development 2024-01-31 sprint to Development 2024-02-14 sprint
- Assigned To deleted (
Lisa Knox)
- Assigned To set to Stephen Smith
- Target version changed from Development 2024-02-14 sprint to Development 2024-02-28 sprint
- Assigned To changed from Stephen Smith to Lisa Knox
- Status changed from New to In Progress
21288-launch-wf-101 @ 60fe1d1bba234f7f5ce6315062aa0a11e2c45e1a - developer-run-tests-services-workbench2: #484 
- ✅ All agreed upon points are implemented / addressed.
- ✅ Anything not implemented (discovered or discussed during work) has a follow-up story.
- ✅ Code is tested and passing, both automated and manual, what manual testing was done is described
- tried to run workflow not in top 100 and succeeded
- ✅ Documentation has been updated.
- ✅ Behaves appropriately at the intended scale (describe intended scale).
- ✅ Considered backwards and forwards compatibility issues between client and server.
- one new api call, shouldn't affect performance
- ✅ Follows our coding standards and GUI style guidelines.
Lisa Knox wrote in #note-14:
21288-launch-wf-101 @ 60fe1d1bba234f7f5ce6315062aa0a11e2c45e1a - developer-run-tests-services-workbench2: #484
- ✅ All agreed upon points are implemented / addressed.
- ✅ Anything not implemented (discovered or discussed during work) has a follow-up story.
- ✅ Code is tested and passing, both automated and manual, what manual testing was done is described
- tried to run workflow not in top 100 and succeeded
- ✅ Documentation has been updated.
- ✅ Behaves appropriately at the intended scale (describe intended scale).
- ✅ Considered backwards and forwards compatibility issues between client and server.
- one new api call, shouldn't affect performance
- ✅ Follows our coding standards and GUI style guidelines.
This LGTM.
- % Done changed from 0 to 100
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous