Approach for task groups assignment

At the moment flow of the tasks require task triage to assign the execution group to the task. In the long term it’s not maintainable and for larger amount of tasks (e.g. approval of 1000 update requests would require 1000 groups assignment).

Simplified Flow:

Open

In the new approach it will be possible to configure the default task group assigned for given task source using the config.

Open

At first user would have to create the groups and create config through Django Admin panel, then groups would be assigned automatically for the tasks.

Stories

1. As a Group Administrator, I want to assign a default task group for each task type through a configuration so that tasks can be automatically assigned to the correct group without manual intervention.

   Acceptance Criteria:

   • Task types can be easily associated with task groups in the Django Admin panel.

   • The system automatically assigns tasks to the configured groups based on their type.

2. As a Task Creator, when I create a new task, I expect it to be automatically assigned to the appropriate group based on its type, so that the task triage process is streamlined and requires less manual effort.

   Acceptance Criteria:

   • New tasks automatically get assigned to the predefined group for their type.

   • Task Creators receive confirmation that the task has been assigned to the correct group.

Approach for bulk updates

Currently if update request was created for the 1000 entities, similarly as in previous step we would have to review 1000 tasks. In order to improve this bulk tasks will be created. This new types of tasks will trigger the action for each atomic task that was created for a given action and resolve them.

Stories

1. As a User, I want to be able to perform bulk approval so that I can efficiently process atomic tasks for bulk actions.

   Acceptance Criteria:

   • User can process single task that will resolve all relevant tasks connected to it.

   • The system processes each task in the bulk action and updates their status accordingly.

2. As a User, when I approve a bulk upload, I expect the system to trigger actions for each atomic task and update their statuses upon completion, so that I can efficiently manage large-scale updates.

   Acceptance Criteria:

   • Bulk approval triggers action for each associated atomic task.

   • Each atomic task's status is updated based on the outcome of the data upload.

   • The bulk task status is updated to reflect the completion of all atomic tasks.

3. As a User, when I reject a bulk upload, I want all associated atomic tasks to be marked as rejected so that I can clearly communicate that the updates should not be processed.

   Acceptance Criteria:

   • Rejecting a bulk task changes the status of all associated atomic tasks to rejected.

   • The bulk task status is updated to reflect the rejection of all atomic tasks.

Improvements for the UI

The view should be changed and present all tasks in one view, no collapsible components for each source. Source should be determined through filter.