<!-- This issue template can be used as a great starting point for feature requests. The section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md). --> ### Release notes Previously, in order to retry a downstream pipeline, you would have to navigate to a pipeline to click the retry button, this is challenging when there are multiple downstream pipelines. Users then have to navigate into each individual pipeline and click the retry action, in this release we've improved the user experience by allowing you to retry the downstream pipeline directly from the pipeline graph without the need to navigate to each pipeline individually. ### Problem to solve In order to retry a downstream pipeline user needs to navigate into the downstream pipeline and click the retry button, this is challenging when there are multiple downstream pipelines that need to be retried. Users then have to navigate into each individual pipeline and click the retry action. ### JTBD When troubleshooting multiple downstream pipelines I want to quickly retry them from one place so I can get the pipeline back to green. ### UX DoD <details><summary>Click to expand</summary> ### UX Definition of Done 1️⃣ **VALIDATION TRACK** **Problem Validation Phase** - [x] Problem is well understood and has been validated - [x] JTBD is well understood and has been validated - [-] PM has communicated the opportunity canvas to stable counterparts and group stakeholders, including the Product Designer and Product Design Manager **Design Phase** - [x] Document the JTBD and UX goal in the issue/epic description - [-] Explore multiple different approaches as a team - [x] Discuss the technical implications with Engineering - [x] Identify any potential cross-team dependencies and include the DRIs in the discussions - [-] Identify a small set of options to validate (Low risk MVC, validation not necessary) - [-] Document the user story(ies) for the MVC - [-] Consider edge cases for each user story - [-] Create prototypes or mockups for each user story - [-] [Pajamas component lifecyle](https://design.gitlab.com/get-started/lifecycle) - [-] Identify component design or pattern update/creation - [-] Discuss the technical implications with Engineering - [-] Pajamas issue is created (within the scope of the MVC) - [x] Update issues/epic descriptions - [x] The appropriate [labels](https://about.gitlab.com/handbook/engineering/ux/ux-department-workflow/#how-we-use-labels) were applied - [-] If changes involve copy, add the ~"Technical Writing" and ~"UI text" labels - [x] Proposed solution(s) identified and documented in the issue/epic description **Solution Validation Phase** - [-] Validate the solution to increase confidence in the proposed solution - [-] Document the solution validation learnings - [-] Product Designer has communicated the solution validation learnings to stable counterparts and group stakeholders, including the Product Design Manager - [-] Update the MVC proposal with relevant insights from the solution validation - [-] Discuss the technical implications with Engineering - [-] Update issue/epic description to contain or link to the findings </details> ### Proposal Allow users to retry a downstream pipeline from the pipeline graph. - Add a retry button to the downstream pipeline (DSP) card on the pipeline graph, so users wont need to leave the graph in order to retry a downstream pipeline. - The retry button will look exactly the same as a retry button on jobs. It'll be placed in the top-right corner of the DSP card, with 8px padding on top and right between the button and the edges of the card. - When the DSP has no failed or canceled jobs, the button won't show up (just like the retry button on the DSP pipeline page) - Permissions should be the same as a permissions to retry the DSP from the pipeline page. If user has no permissions to retry, button won't show up. - When user clicks to retry the DSP, the pipeline will update its status just like it does when you retry it from the pipeline page. #### Further details * When a DSP is successful, the retry button won't show * When you click retry, the button becomes a "cancel" button which will cancel the pipeline retry if you press it * The Cancel button will persist as long as the pipeline is running * If the pipeline is successful, the button disappears from the DSP card, and if it fails then the "Cancel" button becomes "Retry" again <!-- What is the user problem you are trying to solve with this issue? --> <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ * [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager) * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) * [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst) * [Eddie (Content Editor)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#eddie-content-editor) --> ### Implementation plan |Iteration| Description | Link | |--| ------ | ------ | |1|DESIGN/DISCUSSION | https://gitlab.com/gitlab-org/ci-cd/pipeline-authoring/-/issues/53 | |2|Frontend: Add a retry button to a downstream pipeline on the pipeline graph|https://gitlab.com/gitlab-org/gitlab/-/issues/354974 :point_left: you are here| |3|Backend: Differentiate trigger jobs from regular jobs in the UI|https://gitlab.com/gitlab-org/gitlab/-/issues/355751| |4 |Design: Differentiate trigger jobs in the UI|https://gitlab.com/gitlab-org/gitlab/-/issues/340194| |5|Frontend: Differentiate trigger jobs from regular jobs in the pipeline graph |https://gitlab.com/gitlab-org/gitlab/-/issues/356330| |6|Technical spike - expose unexpected behavior when recreating a downstream pipeline|https://gitlab.com/gitlab-org/gitlab/-/issues/355508| |7| Backend issue to recreate downstream pipeline| |8| Frontend issue to recreate downstream pipeline| ### Feature Usage Metrics Should we track the clicks here to see how much this retry feature is used? <!-- How are you going to track usage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ --> <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->