[Story] Enhancement and Redesign of Showing Pipeline Runs on Flow View

[epamLDadayan]

User Story: Enhancement and Redesign of Showing Pipeline Runs on Flow View

---

Description:

As a user, I want a redesigned experience for viewing Pipeline Runs on the Flow View, enabling clearer status differentiation and the ability to view past runs grouped under a History icon for better usability. The new design will ensure easy access to run details, intuitive status indicators, and proper management options for runs across different states.

---

Acceptance Criteria:

1. Redesigned Run Chipset:

• Replace the current Pipeline Run Chipset (Pipeline Run 1 - Status) with a redesigned chipset that includes:
  • Status Icon (based on run state, e.g., in-progress, success, error, stopped).
  • Run # Details (e.g., "Run 1", "Run 2").

2. Grouping of Runs under History Icon:

• When there are 2 or more runs, group all completed or inactive runs under a History Icon located on the top-left side of the Flow View, next to the current run.
• The History Icon only appears if there are 2 or more runs in total.

3. Current Run Display:

• The current run (active or last) is always displayed separately, next to the History Icon and outside the history group for immediate visibility.

4. History Icon Behavior:

• Clicking the History Icon opens a list of available runs grouped under it.
• The list shows each run with:
  • Run number (e.g., "Run 1") and status.
  • Each run's status icon, which visually indicates its completion state.

5. Page Refresh Behavior:

• If the page is refreshed, all runs disappear, except for the current active run (if any).

6. Status Indicators and Icons:

• Each run must include a status icon displayed clearly in both the Flow View and History list:
  • Blue Loading Icon: Indicates a run in progress.
  • Green Checkmark: Indicates a successfully completed run.
  • Red Info Icon: Indicates a run that encountered an error.
  • Orange Stop Icon: Indicates a run that was manually stopped.

7. Deletion of Runs:

• Users can manually delete any run, except:
  • Runs in progress, which must first be manually stopped or allowed to complete before being deleted.
• A Delete Icon appears next to runs that can be deleted.

8. Run Details Popup:

• When a user clicks on any Run Chipset (either current or from History):
  • A popup window opens, displaying detailed information about the selected run.
  • The popup includes run-specific details, such as input/output data, status, timestamps, and errors (if any).

---

Designs:

• https://www.figma.com/design/5vWxC85QBhqbzPU30RP7LH/Alita.-Prompt-Library?node-id=13557-172934&p=f&t=ti2XozjHfKh2ZbwD-0
• https://www.figma.com/design/5vWxC85QBhqbzPU30RP7LH/Alita.-Prompt-Library?node-id=17953-251789&p=f&t=yxgMvbfRHrSdtrft-0

Notes for Developers and QA:

1. History Handling and Behavior:

• Ensure that all runs (except active ones) are grouped appropriately under the History Icon once there are 2 or more runs.
• Test various scenarios for when runs move into History after completion or stopping.

2. Status Colors and Icons:

• Ensure the status icons align with their respective statuses and are visually clear:
  • In-progress: Blue Loading.
  • Success: Green Checkmark.
  • Error: Red Info Icon.
  • Stopped: Orange Stop Icon.

3. Deletion Logic:

• Ensure users can only delete eligible runs (not in-progress runs).
• If a deletion icon is clicked, validate that the run is removed from both the History List and Flow View.

4. Popup Details Modal:

• Ensure run details are displayed properly and fully in the popup modal.
• Test various edge cases for runs with incomplete data, errors, or complex outputs.