L3 - Default As a user, I want to recalculate the priority of an existing task using a REST call, so that the highest priority tasks will be executed first at all times.
Problem
Today, when the variables used to prioritize tasks have been updated by a backend service, users cannot trigger the engine to recalculate the priority of a task with a simple REST call - without duplicating the existing behavior of priority evaluation. **
Scenario:
Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}.
Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}.
Acceptance criteria:
As a User, when I update the variables of an existing task, I can recalculate the priority of a task using a REST call.
This is the controller panel for Smart Panels app
[CAM-11807] As a user, I want to recalculate the priority of an existing task using an API call
| Description |
Original:
As a user, I want to recalculate the priority of an existing task using a REST call, so that updated tasks with higher priority will be executed first.
*Problem* Scenario: Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}. Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}. Now, the variables used to prioritise these tasks have been updated by a backend service. Today, there is no way to trigger the engine to recalculate the priority of a task with a simple REST call - without duplicating existing behaviour of priority evaluation. *Acceptance criteria* *-* As a User, when I update the variables of an existing task, I can recalculate the priority of a task using a REST call. |
New:
As a user, I want to recalculate the priority of an existing task using a REST call, so that updated tasks with higher priority will be executed first.
*Problem* Scenario: Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}. Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}. Now, the variables used to prioritise these tasks have been updated by a backend service. Today, there is no way to trigger the engine to recalculate the priority of a task with a simple REST call - without duplicating existing behaviour of priority evaluation. *Acceptance criteria:* As a User, when I update the variables of an existing task, I can recalculate the priority of a task using a REST call. |
| Mentioned Roles |
| Mentioned Groups |
| Summary | Original: As a user, I want to recalculate the task priority of a given task using an API call | New: As a user, I want to recalculate the priority of an existing task using an API call |
| Description |
Original:
As a user, I want to recalculate the priority of an existing task using a REST call, so that updated tasks with higher priority will be executed first.
*Problem* Scenario: Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}. Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}. Now, the variables used to prioritise these tasks have been updated by a backend service. Today, there is no way to trigger the engine to recalculate the priority of a task with a simple REST call - without duplicating existing behaviour of priority evaluation. *Acceptance criteria:* As a User, when I update the variables of an existing task, I can recalculate the priority of a task using a REST call. |
New:
As a user, I want to recalculate the priority of an existing task using a REST call, so that the highest priority tasks will be executed first at all times.
*Problem* Scenario: Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}. Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}. Now, the variables used to prioritize these tasks have been updated by a backend service. Today, there is no way to trigger the engine to recalculate the priority of a task with a simple REST call - without duplicating the existing behavior of priority evaluation. *Acceptance criteria:* As a User, when I update the variables of an existing task, I can recalculate the priority of a task using a REST call. |
| Mentioned Roles |
| Mentioned Groups |
| Link | New: This issue is related to SUPPORT-6813 [ SUPPORT-6813 ] |
| Description |
Original:
As a user, I want to recalculate the priority of an existing task using a REST call, so that the highest priority tasks will be executed first at all times.
*Problem* Scenario: Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}. Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}. Now, the variables used to prioritize these tasks have been updated by a backend service. Today, there is no way to trigger the engine to recalculate the priority of a task with a simple REST call - without duplicating the existing behavior of priority evaluation. *Acceptance criteria:* As a User, when I update the variables of an existing task, I can recalculate the priority of a task using a REST call. |
New:
As a user, I want to recalculate the priority of an existing task using a REST call, so that the highest priority tasks will be executed first at all times.
*Problem* Today, when the variables used to prioritize tasks have been updated by a backend service, users cannot trigger the engine to recalculate the priority of a task with a simple REST call - without duplicating the existing behavior of priority evaluation. ** Scenario: Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}. Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}. *Acceptance criteria:* As a User, when I update the variables of an existing task, I can recalculate the priority of a task using a REST call. |
| Mentioned Roles |