Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dataset Flows page #233

Closed
zaychenko-sergei opened this issue Nov 14, 2023 · 0 comments · Fixed by #260
Closed

Dataset Flows page #233

zaychenko-sergei opened this issue Nov 14, 2023 · 0 comments · Fixed by #260
Assignees
Labels
enhancement New feature or request

Comments

@zaychenko-sergei
Copy link
Contributor

zaychenko-sergei commented Nov 14, 2023

Follow Figma wireframe closely:

image

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.

  1. 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, ...)
  2. 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)
  3. 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
  4. Each flow should display the initiator. For automated flows, “kamu” with the corporate icon should be used.

  5. Flows should be filterable by status, creator

  6. Flows should be sorted from latest to oldest

  7. Flows should be split by multiple pages with typical navigation

  8. It should be possible to open a detailed view about the flow (separate ticket, but reserve a route).

  9. It should be possible to manually cancel a flow, assuming the logged user has a write permission.

  10. 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
  11. 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
  12. Reserve a text field for advanced filters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
2 participants