You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket assumes creating HTML markup, Angular component part, and services with mocked data.
Integrating with actual GraphQL APIs will be done separately.
Any anonymous or logged in user having canView permission on the dataset may view the represented information about dataset flows history, however only a user having canSchedule permission may trigger manual update, visit scheduling settings, or cancel the scheduled tasks.
Each flow should display a title, based on its origin:
Manual polling update
Scheduled polling update
Cascading Derivative Transformation
Future: push update
Future: other kinds of flows (Compacting, ...)
Each flow should have a 1-line description:
Failed flow: a short reason description, maybe a link to logs
Succeed flow: an outcome summary (ingested N records)
Running/Queued flow:
Polling data from
Running transformation
Future: Processing pushed block
Future: Running dataset compacting maintenance
Canceled flow: who canceled and when)
Each flow should display status information, including::
Status label itself (Running, Completed, …)
Calendar note (in a form like “5 minutes ago, day ago):
Queued flow - when queued
Completed flow - when completed
Duration note:
Running flow - how long it is running by now
Completed flow - how long the process was running
Each flow should display the initiator. For automated flows, “kamu” with the corporate icon should be used.
Flows should be filterable by status, creator
Flows should be sorted from latest to oldest
Flows should be split by multiple pages with typical navigation
It should be possible to open a detailed view about the flow (separate ticket, but reserve a route).
It should be possible to manually cancel a flow, assuming the logged user has a write permission.
It should be possible to quickly):
Enable/Disable dataset flows of all types
Navigate to scheduling settings
Schedule manual tasks, such as Ingest, Execute Transformations
A tile-based widget should indicate status of previous N runs:
Green - complete, Red - failed, Yellow - running or queued (perhaps different colors)?
Hover tooltips should indicate limited summary information
It should be possible to open details from this statistics too
Reserve a text field for advanced filters.
The text was updated successfully, but these errors were encountered:
Follow Figma wireframe closely:
This ticket assumes creating HTML markup, Angular component part, and services with mocked data.
Integrating with actual GraphQL APIs will be done separately.
Any anonymous or logged in user having
canView
permission on the dataset may view the represented information about dataset flows history, however only a user havingcanSchedule
permission may trigger manual update, visit scheduling settings, or cancel the scheduled tasks.Each flow should display a title, based on its origin:
Each flow should have a 1-line description:
Each flow should display status information, including::
Each flow should display the initiator. For automated flows, “kamu” with the corporate icon should be used.
Flows should be filterable by status, creator
Flows should be sorted from latest to oldest
Flows should be split by multiple pages with typical navigation
It should be possible to open a detailed view about the flow (separate ticket, but reserve a route).
It should be possible to manually cancel a flow, assuming the logged user has a write permission.
It should be possible to quickly):
A tile-based widget should indicate status of previous N runs:
Reserve a text field for advanced filters.
The text was updated successfully, but these errors were encountered: