L3 - Default User Story (Required on creation):
As Operations Engineer I want to "Increment Number of Retries" for a process, for which the retries are expired. The first of these retries should be executed in a timely manner. Currently, a retry starts with the last timer element defined in the "retry time cycle" (technical implementation). If that element is e.g. 1 day (see screenshot), it takes one day until the first retry is executed. With a REST call "Set due date" the retry can be triggered instantly. One solution can be to allow "set due date" in the "Increment Number of Retries" job.
https://miro.com/app/board/uXjVO_tEH-M=/?moveToWidget=3458764522472212272&cot=14
Functional Requirements (Required before implementation):
- Allow to "set due date" for "Increment Number of Retries" batch operations
- If the user does not choose to set a due date, the UI informs them what the default behavior is
- Decide: Should setting a due date also be possible for the non-batch operations for incrementing job retries? (see https://docs.camunda.org/manual/7.17/webapps/cockpit/bpmn/failed-jobs/)
Limitations of Scope (Optional):
Hints (Optional):
- See "set removal time" batch operation options for setting "due date"
