fix: FIT-570: Async task assignments user feedback

.mock/definition/actions.yml

@@ -1,31 +1,31 @@
 types:
   ActionsListResponseItemDialog:
     properties:
-      title:
-        type: optional<string>
+      form:
+        type: optional<list<map<string, unknown>>>
       text:
         type: optional<string>
+      title:
+        type: optional<string>
       type:
         type: optional<string>
-      form:
-        type: optional<list<map<string, unknown>>>
     source:
       openapi: openapi/openapi.yaml
     inline: true
   ActionsListResponseItem:
     properties:
+      dialog:
+        type: optional<ActionsListResponseItemDialog>
+      experimental:
+        type: optional<boolean>
       id:
         type: optional<string>
-      title:
-        type: optional<string>
       order:
         type: optional<integer>
       permission:
         type: optional<string>
-      experimental:
-        type: optional<boolean>
-      dialog:
-        type: optional<ActionsListResponseItemDialog>
+      title:
+        type: optional<string>
     source:
       openapi: openapi/openapi.yaml
   ActionsCreateRequestId:
@@ -305,41 +305,6 @@ types:
     source:
       openapi: openapi/openapi.yaml
     inline: true
-  ActionsCreateRequestSelectedItemsIncluded:
-    properties:
-      all:
-        type: boolean
-        docs: No tasks are selected
-      included:
-        type: optional<list<integer>>
-        docs: List of included task IDs
-    source:
-      openapi: openapi/openapi.yaml
-    inline: true
-  ActionsCreateRequestSelectedItemsExcluded:
-    properties:
-      all:
-        type: boolean
-        docs: All tasks are selected
-      excluded:
-        type: optional<list<integer>>
-        docs: List of excluded task IDs
-    source:
-      openapi: openapi/openapi.yaml
-    inline: true
-  ActionsCreateRequestSelectedItems:
-    discriminated: false
-    docs: >-
-      Task selection by IDs. If filters are applied, the selection will be
-      applied to the filtered tasks.If "all" is `false`, `"included"` must be
-      used. If "all" is `true`, `"excluded"` must be used.<br>Examples: `{"all":
-      false, "included": [1, 2, 3]}` or `{"all": true, "excluded": [4, 5]}`
-    union:
-      - type: ActionsCreateRequestSelectedItemsIncluded
-      - type: ActionsCreateRequestSelectedItemsExcluded
-    source:
-      openapi: openapi/openapi.yaml
-    inline: true
   ActionsCreateRequestOrderingItem:
     enum:
       - value: tasks:agreement
@@ -389,6 +354,41 @@ types:
     inline: true
     source:
       openapi: openapi/openapi.yaml
+  ActionsCreateRequestSelectedItemsIncluded:
+    properties:
+      all:
+        type: boolean
+        docs: No tasks are selected
+      included:
+        type: optional<list<integer>>
+        docs: List of included task IDs
+    source:
+      openapi: openapi/openapi.yaml
+    inline: true
+  ActionsCreateRequestSelectedItemsExcluded:
+    properties:
+      all:
+        type: boolean
+        docs: All tasks are selected
+      excluded:
+        type: optional<list<integer>>
+        docs: List of excluded task IDs
+    source:
+      openapi: openapi/openapi.yaml
+    inline: true
+  ActionsCreateRequestSelectedItems:
+    discriminated: false
+    docs: >-
+      Task selection by IDs. If filters are applied, the selection will be
+      applied to the filtered tasks.If "all" is `false`, `"included"` must be
+      used. If "all" is `true`, `"excluded"` must be used.<br>Examples: `{"all":
+      false, "included": [1, 2, 3]}` or `{"all": true, "excluded": [4, 5]}`
+    union:
+      - type: ActionsCreateRequestSelectedItemsIncluded
+      - type: ActionsCreateRequestSelectedItemsExcluded
+    source:
+      openapi: openapi/openapi.yaml
+    inline: true
 service:
   auth: false
   base-path: ''
@@ -418,20 +418,20 @@ service:
             project: 1
           response:
             body:
-              - id: predictions_to_annotations
-                title: Create Annotations From Predictions
-                order: 91
-                permission: tasks.change
-                experimental: false
-                dialog:
-                  title: Create Annotations From Predictions
+              - dialog:
+                  form:
+                    - key: value
                   text: >-
                     Create annotations from predictions using selected
                     predictions set for each selected task. Your account will be
                     assigned as an owner to those annotations.
+                  title: Create Annotations From Predictions
                   type: confirm
-                  form:
-                    - key: value
+                experimental: false
+                id: predictions_to_annotations
+                order: 91
+                permission: tasks.change
+                title: Create Annotations From Predictions
       audiences:
         - public
     create:
@@ -473,6 +473,12 @@ service:
                 Manager Filters.<br>Example: `{"conjunction": "or", "items":
                 [{"filter": "filter:tasks:completed_at", "operator": "greater",
                 "type": "Datetime", "value": "2021-01-01T00:00:00.000Z"}]}`
+            ordering:
+              type: optional<list<ActionsCreateRequestOrderingItem>>
+              docs: >-
+                List of fields to order by. Fields are similar to filters but
+                without the `filter:` prefix. To reverse the order, add a minus
+                sign before the field name, e.g. `-tasks:created_at`.
             selectedItems:
               type: optional<ActionsCreateRequestSelectedItems>
               docs: >-
@@ -481,12 +487,6 @@ service:
                 `"included"` must be used. If "all" is `true`, `"excluded"` must
                 be used.<br>Examples: `{"all": false, "included": [1, 2, 3]}` or
                 `{"all": true, "excluded": [4, 5]}`
-            ordering:
-              type: optional<list<ActionsCreateRequestOrderingItem>>
-              docs: >-
-                List of fields to order by. Fields are similar to filters but
-                without the `filter:` prefix. To reverse the order, add a minus
-                sign before the field name, e.g. `-tasks:created_at`.
         content-type: application/json
       examples:
         - query-parameters:
@@ -500,14 +500,14 @@ service:
                   operator: greater
                   type: Number
                   value: 123
+            ordering:
+              - tasks:total_annotations
             selectedItems:
               all: true
               excluded:
                 - 124
                 - 125
                 - 126
-            ordering:
-              - tasks:total_annotations
       audiences:
         - public
   source:

.mock/definition/activityLog.yml

@@ -71,14 +71,14 @@ service:
         - response:
             body:
               - data:
-                  - id: 1
-                    user_id: 1
+                  - datetime: '2024-01-15T09:30:00Z'
                     email: email
-                    request_url: request_url
+                    id: 1
                     request_method: request_method
+                    request_url: request_url
                     response_code: response_code
-                    datetime: '2024-01-15T09:30:00Z'
-                recordsTotal: 1
+                    user_id: 1
                 recordsFiltered: 1
+                recordsTotal: 1
   source:
     openapi: openapi/openapi.yaml

.mock/definition/annotationHistory.yml

@@ -28,22 +28,22 @@ service:
       examples:
         - response:
             body:
-              - id: 1
+              - action: prediction
+                annotation_id: 1
                 comment: comment
+                comment_id: 1
+                created_at: '2024-01-15T09:30:00Z'
+                created_by: 1
+                draft_id: 1
+                id: 1
+                lead_time: 1.1
                 organization_id: 1
                 project_id: 1
-                annotation_id: 1
-                draft_id: 1
-                review_id: 1
-                task_id: 1
                 result:
                   key: value
-                lead_time: 1.1
-                action: prediction
+                review_id: 1
                 started_at: '2024-01-15T09:30:00Z'
-                created_at: '2024-01-15T09:30:00Z'
-                created_by: 1
-                comment_id: 1
+                task_id: 1
     api_annotation_history_destroy:
       path: /api/annotation-history/
       method: DELETE
@@ -93,22 +93,22 @@ service:
               next: http://api.example.org/accounts/?page=4
               previous: http://api.example.org/accounts/?page=2
               results:
-                - id: 1
+                - action: prediction
+                  annotation_id: 1
                   comment: comment
+                  comment_id: 1
+                  created_at: '2024-01-15T09:30:00Z'
+                  created_by: 1
+                  draft_id: 1
+                  id: 1
+                  lead_time: 1.1
                   organization_id: 1
                   project_id: 1
-                  annotation_id: 1
-                  draft_id: 1
-                  review_id: 1
-                  task_id: 1
                   result:
                     key: value
-                  lead_time: 1.1
-                  action: prediction
+                  review_id: 1
                   started_at: '2024-01-15T09:30:00Z'
-                  created_at: '2024-01-15T09:30:00Z'
-                  created_by: 1
-                  comment_id: 1
+                  task_id: 1
   source:
     openapi: openapi/openapi.yaml
 types: