Rework the behavior of Toasts for Run, Stop and Replay

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Reproduction steps

      1. Go to a branch tab
      2. Click the run button of a branch
      3. Toast pops up "queued"

      Expected (as per JENKINS-35813)

      1. Go to a branch tab
      2. Click on the run button of a branch
      3. Toast pops up "OPEN" where clicking open will open the result modal for the run in the queued state

      Revised A/C

      1. Clicking a Run or Replay button should immediately produce a "Started" toast with an "OPEN" link that navigates the user to Run Details. No "Queued" toast should be displayed.
      2. Clicking a Stop button should immediately produce a "Stopping" toast. No further "Stopped" toast is necessary.

      Tech Notes

      1. As part of these refinements, personalization should be updated to use the new RunButton and ReplayButton components.
      2. Try to remove any of the "capabilities" code in DashboardCards by leveraging some new capabilities code.
      3. Try to remove any use of IfCapability in dashboard

            Assignee:
            Cliff Meyers
            Reporter:
            James Dumay
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: