-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Categories:
- admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios)
- operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios)
- Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios)
Implementation:
- I can filter the user operation log query by category (including multiple categories)
- The category is persisted in the database (=> this should probably be covered an index, see
CAM-10129) - old log entries remain without category and are not returned by the category filter => this means they will not be available in the new frontend
- the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist)
This is the controller panel for Smart Panels app
[CAM-9920] User operation log includes category
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 12876 ] |
| Description |
Original:
Categories:
* admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios) * operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios) * Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios) |
New:
Categories:
* admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios) * operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios) * Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios) * I can filter the user operation log query by category (including multiple categories) * the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist) |
| Description |
Original:
Categories:
* admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios) * operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios) * Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios) * I can filter the user operation log query by category (including multiple categories) * the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist) |
New:
Categories:
* admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios) * operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios) * Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios) * I can filter the user operation log query by category (including multiple categories) * The category is persisted in the database * the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist) |
| Description |
Original:
Categories:
* admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios) * operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios) * Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios) * I can filter the user operation log query by category (including multiple categories) * The category is persisted in the database * the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist) |
New:
Categories:
* admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios) * operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios) * Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios) * I can filter the user operation log query by category (including multiple categories) * The category is persisted in the database (=> this should probably be covered an index) * the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist) |
| Description |
Original:
Categories:
* admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios) * operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios) * Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios) * I can filter the user operation log query by category (including multiple categories) * The category is persisted in the database (=> this should probably be covered an index) * the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist) |
New:
Categories:
* admin (operations an administrator would trigger, i.e. Camunda Admin usage scenarios) * operator (operations an operator would trigger, i.e. Camunda Cockpit usage scenarios) * Optional: task worker (operations a task worker would trigger, i.e. Camunda Tasklist usage scenarios) Implementation: * I can filter the user operation log query by category (including multiple categories) * The category is persisted in the database (=> this should probably be covered an index) * old log entries remain without category and are not returned by the category filter => this means they will not be available in the new frontend * the categories are statically defined for each operation (e.g. assigning a task to a user is in the task worker category, although it can be done from both cockpit and tasklist) |
| Assignee | New: Tobias Metzke-Bernstein [ tobias.metzke ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Assignee | Original: Tobias Metzke-Bernstein [ tobias.metzke ] | New: Nikola Koevski [ nikola.koevski ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
| Remaining Estimate | New: 0 minutes [ 0 ] | |
| Original Estimate | New: 0 minutes [ 0 ] |