L3 - Default User Story (Required on creation):
I can assign permissions of the resource BATCH to users who should be able to view/update/delete a specific batch or all batches. If interacting with secondary resources of the batch (job definitions, jobs), no permissions are currently enforced. This should be changed to be consistent with jobs that belong to process instances.
Functional Requirements (Required before implementation):
- The relevant permissions on the BATCH resource are enforced for any jobs (see, monitor, execution) and job definitions belonging to that batch
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
Hints (Optional):
- This may require adding a dedicated BATCH_ID reference to the corresponding tables, as it is otherwise fairly hard to figure out in isolation the batch a job or job definition belongs to
This is the controller panel for Smart Panels app
[CAM-13479] Batch permissions cover operations on the corresponding jobs and job definitions
| Summary | Original: Batch permissions cover the belonging jobs and job definitions | New: Batch permissions cover operations on the corresponding jobs and job definitions |
| Link | New: This issue is depended on by SUPPORT-8759 [ SUPPORT-8759 ] |
| Description |
Original:
h4. User Story (Required on creation):
When creating a batch, I can assign permissions of the resource {{BATCH}} to users who should be able to view/update/delete the batch. If interacting with secondary resources of the batch (job definitions, jobs), no permissions are currently enforced. This should be changed to be consistent with jobs that belong to process instances. h4. Functional Requirements (Required before implementation): * The relevant permissions on the {{BATCH}} resource are enforced for any jobs (see, monitor, execution) and job definitions belonging to that batch h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): h4. Hints (Optional): * This may require adding a dedicated {{BATCH_ID}} reference to the corresponding tables, as it is otherwise fairly hard to figure out in isolation the batch a job or job definition belongs to |
New:
h4. User Story (Required on creation):
I can assign permissions of the resource {{BATCH}} to users who should be able to view/update/delete a specific batch or all batches. If interacting with secondary resources of the batch (job definitions, jobs), no permissions are currently enforced. This should be changed to be consistent with jobs that belong to process instances. h4. Functional Requirements (Required before implementation): * The relevant permissions on the {{BATCH}} resource are enforced for any jobs (see, monitor, execution) and job definitions belonging to that batch h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): h4. Hints (Optional): * This may require adding a dedicated {{BATCH_ID}} reference to the corresponding tables, as it is otherwise fairly hard to figure out in isolation the batch a job or job definition belongs to |
| Mentioned Roles |
| Mentioned Groups |
| Labels | New: potential_for_7.16 |
| Labels | Original: potential_for_7.16 | New: potential_for_7.16 potential_for_7.17 |
| Labels | Original: potential_for_7.16 potential_for_7.17 | New: batch potential_for_7.16 potential_for_7.17 |
| Labels | Original: batch potential_for_7.16 potential_for_7.17 | New: batch |