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"
This is the controller panel for Smart Panels app
[CAM-14601] I can change a job's due date when I set the retries to > 0 again
| Link | New: This issue is related to SUPPORT-13262 [ SUPPORT-13262 ] |
| Attachment | New: image-2022-05-12-13-47-33-581.png [ 51960 ] | |
| Description |
Original:
*User Story (Required on creation):*
As Operations Engineer I want to restart a process, for which the retries are already expired. The restart should happen at a defined point in time with one operation. Currently, two steps are necessary. This feature allows to trigger a retry and set the "due date" for the execution in one step which allows easy restart without a lot of clicking. *Functional Requirements (Required before implementation):* * Allow defining "due date" in "Set retries of Jobs belonging to the process instance" batch operation * Allow defining "due date" in Process definition view and Process instance -> Incidents *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
New:
*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 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. !image-2022-05-12-13-47-33-581.png! *Functional Requirements (Required before implementation):* * Allow defining "due date" in "Set retries of Jobs belonging to the process instance" batch operation * Allow defining "due date" in Process definition view and Process instance -> Incidents *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
| Description |
Original:
*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 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. !image-2022-05-12-13-47-33-581.png! *Functional Requirements (Required before implementation):* * Allow defining "due date" in "Set retries of Jobs belonging to the process instance" batch operation * Allow defining "due date" in Process definition view and Process instance -> Incidents *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
New:
*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 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. !image-2022-05-12-13-47-33-581.png! https://miro.com/app/board/uXjVO_tEH-M=/?moveToWidget=3458764522472212272&cot=14 *Functional Requirements (Required before implementation):* * Allow defining "due date" in "Set retries of Jobs belonging to the process instance" batch operation * Allow defining "due date" in Process definition view and Process instance -> Incidents *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
| Description |
Original:
*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 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. !image-2022-05-12-13-47-33-581.png! https://miro.com/app/board/uXjVO_tEH-M=/?moveToWidget=3458764522472212272&cot=14 *Functional Requirements (Required before implementation):* * Allow defining "due date" in "Set retries of Jobs belonging to the process instance" batch operation * Allow defining "due date" in Process definition view and Process instance -> Incidents *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
New:
*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 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. !image-2022-05-12-13-47-33-581.png! [https://miro.com/app/board/uXjVO_tEH-M=/?moveToWidget=3458764522472212272&cot=14] *Functional Requirements (Required before implementation):* *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
| Description |
Original:
*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 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. !image-2022-05-12-13-47-33-581.png! [https://miro.com/app/board/uXjVO_tEH-M=/?moveToWidget=3458764522472212272&cot=14] *Functional Requirements (Required before implementation):* *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
New:
*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 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. !image-2022-05-12-13-47-33-581.png! [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 *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
| Sprint | New: SOON [ 95 ] |
| Rank | New: Ranked higher |
| Sprint | Original: SOON - Customer commitment [ 95 ] | New: Release 7.19 [ 123 ] |
| Description |
Original:
*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 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. !image-2022-05-12-13-47-33-581.png! [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 *Limitations of Scope (Optional):* *Hints (Optional):* * See "set removal time" batch operation options for setting "due date" |
New:
*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 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. !image-2022-05-12-13-47-33-581.png! [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" |
| Fix Version/s | New: 7.19.0 [ 16008 ] |